Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
Here's an example of how this would be useful:
We use the nickname field on the User entity for our employee initials. For our clients, there are up to 5 employees assigned to the client in different roles, and they are linked via lookup fields to the User.
For a view where we want to include all the linked users, we either have to use a lot of column space to show the fullname, or we have ambiguous column headings (showing only "Initials") and show their initials. If you point to the column heading, the popup gives the user enough info to know what role it is, but it would be better to just give the column heading a useful display name.
If "table role="presentation""and its "td"and "tr"children were replaced with "div" *
Adding to this one as by Global Dimension 1 for a customer is DEPT. On my COA, I have all balance sheet accounts setup with Default Dimension Value Code = 000 and Value Posting = Same Code. Logically, I expected the 000 value to default on my AP distributions when entering a Purchase Invoice, but the default DEPT in the Invoice Details section is not defaulting. As a result, the DEPT dimension is blank. I'm not easily able to run reports within BC based on a DEPT value that is null. I can restrict by dimensions with actual values, but blank, spaces or null are not options. For my balance sheet account, I'd like the Same Code to default anywhere that GL account is used.
If the Value Posting is blank or code mandatory and there is a default Dimension Value Code defined, I'd like to see that default on all G/L lines where that account is used UNLESS we are defining a different dimension value in the posting group definition. To that end, it would be nice if we can define default dimensions within a posting group. For example, If I wanted to separate my vendor AP posting by DEPT, I would like to be able to define the GL account as 2000, but I would like all vendors that are in the EMPLOYEE Posting Group to post to DEPT 100 and vendors who are REGULAR to post to everything EXCEPT 000 and 100.
Also, please enable/allow extension of AOSAuthorization for fields DirPerson.BirthDay, BirthMonth, and BirthYear; all of which could be considered personally identifiable information
This filter is a necessity for the flow of our invoice process. It's not feasible to obtain GRN's when processing in excess of 40 invoices for vendors at a time
Work policy can be configured to avoid work-creation. What is needed is:
The ability to RAF to same License plate multiple times without creating work.
A process to create the work, when the RAF to the License plate is completed.
Ability to print labels before work is created.
The issue is the same for Purchase order and transfer order receive without work.
Hi, the absence of this really makes the workflow convoluted for users
They create a purchase invoice then need to go to the PO, check if the PO matches the invoice then check for the GRN document number then go back to the purchase invoice screen then get receipt and find and select the GRN number they've just memorised
And this only works if the PO has only been receipted in full once on one GRN...if, as happens in real life, goods receipting was done in stages, the user needs to cross check each GRN, remember the GRN numbers applicable to the invoice and then go back to get the right lines pulled in...
Rahul - Thank you for posting. It is very important for efficiency.
Other relevant discussion on the yammer group.
any update on the suggestion made by Roberto Stefanetti earlier? We would also need to be able to purchase resources for Jobs and I would imagine this would not be that difficult to implement. It might actually be not more complicated than just accepting the Type::Resource in the validation of Job No. field in the Purchase Line table? At the moment it only accepts Item and G/L Account:
IF NOT (Type IN [Type::Item,Type::"G/L Account"]) THEN
(the code is from Business Central 14 but I think it's still the same)