Views:

Applies to Product - Dynamics 365 Business Central

What’s happening?
The Document Number is not being populated from the No Series assigned on the Project Journal batch or when using the Payment Journal OData API. Instead, the Document Number is being copied from the Project Number when the Project Number field is validated.


Reason:
This is caused by using exposed UX pages as web services. When UX is utilized in this manner, it lacks certain elements such as xrec and currfieldno, which are necessary for proper functionality. Additionally, the Document No. from the page is coming from the web client, but that call does not execute when the page is exposed.


Resolution:

  1. For the Project Journal issue, disable the feature "Document No. Is Project No." to allow the Document Number to be populated from the No Series assigned on the Project Journal batch.
  2. For the Payment Journal OData API issue, do not use the exposed UI pages and web services. Instead, utilize the standard API provided by Microsoft for customer payments.
  3. Refer to the following link for the standard API documentation:
  4. Microsoft API Reference
  5. If the issue persists, gather the following information for further investigation:
  6. Confirm if the issue occurs only with the API or also manually in Business Central.
  7. Specify whether a POST or PATCH request is being sent to the API and provide an example of the request and response.
  8. Test with different payment journals to see if the issue occurs in all of them or just in a specific one.
  9. Check if there are any custom extensions that might affect the payment journal behavior.
  10. Ensure the account used for the API has the necessary permissions in Business Central.
  11. Provide the Tenant ID and the environment name where this issue is occurring.
  12. Include the last attempt timestamp (date, time, and time zone).
If further assistance is needed, consider raising a ticket with the product team for a more in-depth analysis.