SoftPro Developer Forum

I am unable to replicate your error. I am using this code fragment to generate an error for a custom order property when the order is saved. Have you restarted the server to make sure all the new custom fields are loaded? Is the custom type a "Text" type? os.OrderSaving += (o, e) => { e.Ad...

OrderOverlaySettings is a wrapper around various collections that hold references to items you want to import from a source order into your current order. All of the properties are readonly since they are collections that you will add items you want to import (i.e. to specify a contact to import, ge...

Please share your source code for this section.

OrderOverlaySettings will add items to your current order. You must then save the current state of the order to retain the changes. So the steps would be: Open or create an order with IOrderStore.NewOrder(...), IOrderStore.OpenOrder(...), or use active order. Modify the order (many any ways includin...

The logic is still sound. SelectServer is only used to get the IOrderStore and IErrorList interfaces. My point in your original problem was that your "originalAttachment.AttachmentPath" specified a file and not a folder in the attachments - that's why the interface was returning an IAttach...

Looks like your path fetches an attachment file - not an attachment folder. You need to be mindful of what type of object your path specifies. Try changing your cast and folderItem type to IAttachmentFile.

It is up to the developer to use whatever business logic is necessary. Select passes in the context from the order (in your case the Address object) and the matching lookup table rows (with all the colums for each row). It is possible that your logic may need to examine multiple columns to validate ...

You don't need to do a second search on the table in the handler. Select passes you the matching possibilities in the LookupRowSelectionEventArgs. You can get to each column entry in the table by referencing them as below. See the ILookupRow interface in the SDK for ways to reference the columns. IL...

We have identified this is a known issue that has been logged. No ETA at this time.

This is to let you know that we are working on a resolution to this issue. The July 4th holiday has interfered with a more prompt response. Sorry.