Aaron LaBounty

Gotcha. Thanks!

We've had a few clients that needed to import manual payments with quite a few lines on a regular basis and we wrote them a C# command line utility that runs in the background, parses their .csv file, then uploads it to Intacct via the API. If this is something that needs to be done on a regular basis I agree with Louis and think that may be a better option than using Postman. You could also build a custom application inside Intacct that would do the same thing.

Thanks Louis! I found the Export def button, for me it only appears Step 4 - Select deployment options, so unless you navigate to that specific page you won't see it. Something I'm sure most people already know, but I did not. Attached is the screenshot you requested. I'm guessing it can't be included in a customization package, but I thought I'd ask.

I'm trying to create an XML Package with a Custom Field that is a sequence and linked to a new custom document sequence, that custom document sequence, and a smart link. However, I can't find a complete schema that covers all these different items, and can't find examples of these either I've reviewed both the support article "Customization Services - How to create an XML package of Smart Rules" and https://developer.intacct.com/customization-services/customization-packages/#create-a-package and they were somewhat helpful, but left a lot of questions like (see below). Is there some other documentation or Sage U class that has more information? Or is it just a lot of trial and error? Questions When I view one of these custom items and Print To -> XML I end up with a lot of elements I don't believe are needed, like Root, Company, and Rec elements, and RecordNo field in the rec element. How do I know what elements to actually include the the customization package? In the example I found for a Smart Link in a customization package, there is a <smartLink> then <smartLinkID> element, but when I Print To -> XML on my Smart Event, I don't see a <smartEvent> or <smartEventID> element in the XML that's produced, so do those need to be added manually? If so are <smartEvent> or <smartEventID> the correct elements to use? Is there a way to include the custom document sequence in this customization package?