SoftPro Developer Forum

You can use the Select SDK to add new functionality by creating Shell Packages that add new screens to the user interface or Server Packages that provide enterprise-wide functionality or validations. The API can be used to access all elements of ProTrust through the ILedgersManager, ITransactionMana...

Sorry, but this forum cannot send hotfixes to customers. Please talk to your SoftPro Customer Service Representative to request software.

Sorry, but this cannot be modified by the API at this time. The only options for the basis are those provided by the SPAdmin screen.

You can always put in a formula or custom order rule in an amount field to compute the value. This would allow you to use any order field(s) you wish.

Fantastic! This is the way packages are typically developed since it's quick and easy.

Yes. You will always get license errors in the release build unless you have a license for the package. Sorry, I was unclear. I wanted you to create a debug package and run it on your local development system without any of the MSI packaging or deploying to a remote server that you do. I want to tes...

We need to establish a baseline of functionality. Put a copy of Select and the Select SDK on your local development machine. Then create a shell application in VS2010 in debug build using the steps in the SDK (How-To -> Shell Package Development) on your local system. Does this work?

The SA(All Sellers) and BA(All Buyers) contacts represent the collection of Sellers and Buyers respectively. Select makes this group contact available with the top level AllBuyers and AllSellers objects. For instance, using your example: dynamic order = iOrder; order.CDFs[0].OriginationChargeSection...

A followup for others viewing this thread: Select packages must be built with Visual Studio 2010 at this time. There are plans to update the Select SDK and the package build process to VS2015 in the first quarter of 2016 as we incorporate the 4.6 .NET Framework. But until then, no other Visual Studi...

Is it possible that your code is actually not being installed and you are viewing an older version of the build? Delete then reload the Exp hive to get a fresh hive that has never had a copy of your buttons installed and verify that your original two buttons appear and not your third. Create New Exp...