SoftPro Developer Forum

Typically, this error results from a failure in the constructor of the snap section or a failure in the Initialize(...) method of the snap section. That would be the point where I would start to look.

Due to changes made to support the new HUD GFE, ProForm and DataCollector no longer update an existing row. Rather, they delete the existing row and insert a new row. This may be the cause of the trigger not firing.

Sanjay, The "Name" property on the IBuyer is automatically populated through business rules unless there exists a user-entered value within that property. The following code populates the people of a joint buyer. It properly updates the "Name" property of the IBuyer and appears p...

Yes, there is a way to specify the template(s) to be used during order creation. Within the OrderCreationSpec class, there is a property named Templates that is a List<string> (or List(Of String) in Visual Basic). You can use the Add(...) method to add the name of the template you wish to use. For e...

The ChecklistTask and RequestedTask collections on the IOrder interface include a Remove(..) method and a RemoveAt(...) method. The Remove method takes as its parameter the object to remove; the RemoveAt method takes as its parameter the index into the collection of the object to remove. The followi...

You will have to have delete permission for notes. Under the ProForm\Order\General category of permissions, there is a permission called Note with the rights of Add, Edit, Delete. You or a group you belong to mush have the Delete right in order to delete notes.

This has been identified as a bug in the application. As a workaround, deleted the notes individually off of the requested/checklist task first before deleting the task, itself.

Let me research this and get back to you.

That column is being ignored. The objects that support custom fields are listed in the custom field editor's context dropdown in SPAdmin.

IChecklistTask and IRequestedTask objects do not support custom fields. They will not have the GetCustomField(...) and SetCustomField(...) methods on the interfaces.