Hi,
We have a third-party expense reporting solution (DynamicPoint) that passes General Journal batches into NAV via a web service that consumes Page 39 (General Journal).
We are upgrading from NAV2009 to NAV2016, and are testing these web services in 2016.
Using the same identical setup, when DP attempts to send a Gen. Journal batch to 2016, it shows an error "Field Balance is Read-Only".
There IS a field on the page called "Balance" - and it is in fact Read-only (it is a calculated field). The DP developers say they are not passing this value in their XML (we are attempting to verify this).
HOWEVER, they have noticed (and we have confirmed) that if we set up the Journal Batch with a "Bal. Account No.", then the error is not received.
We do not have Bal. Account No.'s defined for any of our batches, and in fact, we do not want to use them because we use 2 different Dimension Sets on the Debit and Credit sides of the transactions.
This is not a problem in 2009, and Page 39 in 2009 has the same "Balance" field.
Has anyone run across a problem like this? We are on NAV2016 CU5.
Thanks
Ron
We have a third-party expense reporting solution (DynamicPoint) that passes General Journal batches into NAV via a web service that consumes Page 39 (General Journal).
We are upgrading from NAV2009 to NAV2016, and are testing these web services in 2016.
Using the same identical setup, when DP attempts to send a Gen. Journal batch to 2016, it shows an error "Field Balance is Read-Only".
There IS a field on the page called "Balance" - and it is in fact Read-only (it is a calculated field). The DP developers say they are not passing this value in their XML (we are attempting to verify this).
HOWEVER, they have noticed (and we have confirmed) that if we set up the Journal Batch with a "Bal. Account No.", then the error is not received.
We do not have Bal. Account No.'s defined for any of our batches, and in fact, we do not want to use them because we use 2 different Dimension Sets on the Debit and Credit sides of the transactions.
This is not a problem in 2009, and Page 39 in 2009 has the same "Balance" field.
Has anyone run across a problem like this? We are on NAV2016 CU5.
Thanks
Ron