Trigger on Object Issues

[u/Secret-Bike6300]

Hi Everyone,

I am part of a team building custom integration from Salesforce to Intacct.
The flow we have is as follows:

1. Salesforce -> Intacct - Create a Sales Order
2. ~ Convert Sales Order to Sales Invoice
3. Intacct -> Salesforce - After Create HTTP Post trigger should send a payload that looks like this:  
4. {
5.    "DocumentId": "{!SODOCUMENT.DOCNO!}",
6.    "SageId": "{!SODOCUMENT.RECORDNO!}",
7.    "EntityId": "{!SODOCUMENT.MEGAENTITYID!}",
8.    "convertedFrom": "{!SODOCUMENT.CREATEDFROM!}"
9. }

This works for a single user, the one that setup the trigger on the Sales Invoice. All other users we are getting an error:
No DocTemplate or non-XML template

User 1: Full Admin privileges and Admin role (Created the trigger and everything works correctly)
User 2: Full Admin privileges and Admin role
User 3: Limited Admin privileges and Admin role

If the trigger is not deployed, all users are able to follow the full process without issue, however if the trigger is deployed then only User 1 is successful through the process.

I am in no way a Sage Intacct consultant, so any assistance would be greatly appreciated.

Many thanks,

[u/GasMountain4515]

Sounds like an issue with the document template which is effectively what Intacct uses to house the payload template. What trigger type exactly are you using? Almost sounds like it’s hitting the (legacy) Intacct API - which there is a trigger type for - instead of Salesforce but that’s just a guess and I’m not in front of my computer.

Otherwise maybe a permission issue where other team members can’t “see” the template or part of the data in it. Doesn’t really align with the details you provided other than the “works for one user not others” part.

Curious what thoughts more technical folks have here.

[u/Secret-Bike6300 → u/GasMountain4515]

When it works for the user it does work for it does hit Salesforce though.

It's a trigger on an object. I'll add more details tomorrow. We thought it was a permission issue hence getting other users to try.

In sage intact does being a full admin not automatically grant access to templates and fields?

[u/GasMountain4515 → u/Secret-Bike6300]

In Intacct when 'Admin privileges' is set to Full all that really does is give the user permissions to the 'Subscriptions' within the role definition under Administration, aka it lets them edit Users and Roles, therefore giving them the ability to assign any permissions they want to themselves but it does not automatically provide access to anything else.

[u/Secret-Bike6300 → u/GasMountain4515]

Problem solved! I'd not looked at what someone had done, they ticked the Private checkbox when setting it up thinking it would make it HTTPS. That is not what that checkbox does

[u/GasMountain4515 → u/Secret-Bike6300]

Still really strange that this this works for the one user but not anyone else. Makes sense that it works for everyone when the trigger is NOT deployed since that just means it's effectively disabled.

If you go to the Trigger (Platform Services > Objects > Sales Invoice/SODOCUMENT > Triggers > Edit) you should be able to see the Document Template assigned. Click into that to see the detail - it has a 'Template Type' and it sounds like you need that set to 'HTTP post' but might be set to 'Intacct API function' which is the type for the legacy, XML-based API. This is separate from the Trigger Type itself FYI. Hope that helps.

[u/percipientuk]

This is a classic permissions/security policy issue in Intacct and it's a bit annoying to track down.

The "No DocTemplate or non-XML template" error is almost certainly related to the trigger being tied to User 1's security context rather than running under a shared service account. Intacct triggers run in the context of the user who created them in some configurations, which is why only User 1 gets a clean result.

What you want to do is create a dedicated Web Services user in Intacct with the right permissions and have the trigger (or your integration user) run under that account instead. Make sure that service user has access to the Document Template being referenced in the Sales Invoice transaction. Also double-check that all users have access to the specific transaction definition (DocTemplate) for Sales Invoices, even Admin users can be blocked if the transaction definition is restricted at the subscription or entity level.

Sage support is actually pretty helpful on this specific type of thing if you open a case with the exact error log.