Marco de Vries Senior Consultant

When there is a projectcontract with over more than 200 Contractlines, the generation of an invoice is not always possible due to a time-out. With every contractline for a different project customer the system creates a projectcustomer line for a billing percent of 0. This means when you are creating an invoice the system will make an invoice of 0 and also deletes this invoice. In my opinion the system should not generate these zero invoices and only have to look for billing percentages higher than 0.

This issue has been acknowledged by Microsoft and they ran a script to solve this issue for two projectcontracts (over 300 and 500 contractlines):

"I would like to share a bit more information, regarding the overall advise coming from the product team on the creation of many [Project Contract Customer] and [Project Contract Line Customer]] records that have 0 in the [split billing percent]. 

 The advice is that they should not be created as they do not result in any Actuals and no invoices are kept for them as once a contract is invoiced, the system will try to create invoice for each customer listed in the [Contract Line Customer Customer] record, realize that invoice has 0 amount, and no invoice line details to invoice then delete that created invoice. As result of the above-mentioned steps, the overall invoice creation process for contract will suffer great performance hit."

In the document "https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/api/dynamics_customer_get" the columns are described that will be in the response of a Get Customers request. However, the column "Language" is missing.

Please add this column to the response.

Below you'll find an example of all the columns that are returned:

"id": "f2a5738a-44e3-ea11-bb43-000d3a2feca1",

"number": "10000",

"displayName": "Adatum Corporation",

"type": "Company",

"addressLine1": "192 Market Square",

"addressLine2": "",

"city": "Atlanta",

"state": "GA",

"country": "US",

"postalCode": "31772",

"phoneNumber": "",

"email": "robert.townes@contoso.com",

"website": "",

"taxLiable": true,

"taxAreaId": "90196a90-44e3-ea11-bb43-000d3a2feca1",

"taxAreaDisplayName": "ATLANTA, GA",

"taxRegistrationNumber": "",

"currencyId": "00000000-0000-0000-0000-000000000000",

"currencyCode": "USD",

"paymentTermsId": "04a5738a-44e3-ea11-bb43-000d3a2feca1",

"shipmentMethodId": "00000000-0000-0000-0000-000000000000",

"paymentMethodId": "3b196a90-44e3-ea11-bb43-000d3a2feca1",

"blocked": " ",

"lastModifiedDateTime": "2020-08-21T07:38:44.293Z"

It is not possible to create a quarterly invoice frequency so e.g. Advances invoices can't be generated automatically every quarter.

The options for the invoice frequency are Weekly, Monthly and Biweekly and it would nice to extend this with a Quarterly option.

Project Operations should support the localization of the decimal and thousands separator key (typically a period or comma character) when entering numeric values in fields. On most non-US keyboards, using the "." or "," as a thousandths or decimal separator from the keyboard's numeric keypad doesn't result in the correct separator in PO. For example, a value of 123,456 got entered as 123.456.

The decimal separator should match the region specified in the Personalization Settings (tab Formats). Similar to working in Excel, the output of the decimal separator key is consistent across fields of any data type.

This issue already has been solved in Business Central 09/08/2022 and it should do the same in PO: https://learn.microsoft.com/en-us/dynamics365-release-plan/2021wave2/smb/dynamics365-business-central/support-localized-decimal-separator-numeric-keypads