NAV2016 Using General Journal Page 39 as web service - Field Balance is Read-only

rsaritzky

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

rsaritzky

Thank you for the reply. I did more investigation on how this page works, and it's either a bug or it's "standard behavior" of this page which means it is not compatible when used as a web service.

When you enter a General Journal line and there is no balancing account, the page recalculates the "Balance" field and displays it. So if you enter a GJ line for, say $50.00, the Balance field will then display 50.00.

The ISV's software was returning a value of $0.00 in the "Balance" field (they were not bothering to update the field at all, so the default value of 0.00 was being returned.) So NAV thought apparently that it was trying to update this field.

We did in fact test it exactly the way you recommended - I created a copy of the GJ page but removed the Balance-related fields. The transactions were accepted fine using this version of the page.

We are trying to use the ISV's solution "vanilla", so we are now attempting to convince them to include a custom GJ page or modify their code to update the value of the "Balance" field if needed.

Thanks.

Ron

Kishorm

Sounds like a bug which you should report to Microsoft.

In the meantime I can see 2 possible workarounds for this issue...

1) Create a new page which is a copy of the journal but without the balance field on it

OR

2) Amend the journal so that the code that calculates the balance is only called when GUALLOWED is true

rsaritzky

Thank you for the reply. I did more investigation on how this page works, and it's either a bug or it's "standard behavior" of this page which means it is not compatible when used as a web service.

When you enter a General Journal line and there is no balancing account, the page recalculates the "Balance" field and displays it. So if you enter a GJ line for, say $50.00, the Balance field will then display 50.00.

The ISV's software was returning a value of $0.00 in the "Balance" field (they were not bothering to update the field at all, so the default value of 0.00 was being returned.) So NAV thought apparently that it was trying to update this field.

We did in fact test it exactly the way you recommended - I created a copy of the GJ page but removed the Balance-related fields. The transactions were accepted fine using this version of the page.

We are trying to use the ISV's solution "vanilla", so we are now attempting to convince them to include a custom GJ page or modify their code to update the value of the "Balance" field if needed.

Thanks.

Ron