Open okmotsan opened 2 years ago
@okmotsan, interesting find...... we are going to look into this and get this resolved.... I'll keep you posted.
@okmotsan, can you share a snippet or example payload with sensitive information removed? We've researched internally and would like to verify how you're sending.
`<?xml version="1.0" encoding="utf-8"?>
Is there any ETA for when this can be fixed? For our use case we have custom fields on both the Invoice and Credit (AR Adjustment) but only the Invoice appears to support populating the customer fields via the API
@okmotsan, waiting for a response on a question I have from the team responsible on this. Based on their response, I'll let you know what can be done, if anything.
Was this ever fixed?
@dylan-holt-sage, was this fixed ? I am having the same trouble with BillCreate object. The SDK lets me pass the custom fields and returns a status of success as well but while retrieving back that bill record, I don't get the custom fields in the response.
There appears to be a contradiction. In the ArAdjustmentCreate class in the WriteXml function it outputs the CustomFields into the XML data. However, in the API docs on the Intacct website there doesn't appear to be support for custom fields for the create_aradjustment XML API call and this seems to be true as when I send the request from .NET with custom fields set for an ArAdjustmentCreate object then I get an error indicating that the custom field node is not expected.
However in Intacct under the Platform Services it does allow me to create custom fields for the AR Adjustment object.
Also the counterpart in the payables (AP Adjustment) does appear to support custom fields.
TL;DR; why doesn't the AR Adjustment support custom fields via the API? It looks partially implemented but broken