Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
If you use Electronic reporting framework to send collection letters, you can utilize organization's email templates managing email subject, body and recipient addresses. See https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/analytics/er-generate-printable-fti-forms?toc=/dynamics365/finance/toc.json#use-the-sample-er-format-to-configure-email-destinations for more. Did you consider this option?
I like this idea
This would be useful
This is a good idea
Proposing additional CBD/ER Destinations enhancements to this idea:
- "Preview"-buttons should only trigger "Screen" and "File"(?) destinations for CBD reports
- Don't for throw error/warning message when email address is not found. Should be possible to turn off the warning/error if you only expect to send emails according to the customer contact information(eg. purposes).
- Instead show message when email(s) are successfully sent
- Create a log or archive of the generated print destinations to avoid mistakes of duplicate send-outs to external parties
I agree !!
I think specially this is very interesting for the item variants. If they could have attributes, the catalog will be much more flexible and searchable.
Also would be nice to have a matrix in order lines, where you could assort the Order Line Quantity. For example, say a shirt comes in 5 colors and 5 sizes, We would create 25 item variants with 2 attributes, size and color.
In stead of creating 25 order lines when we need this product, we would only create 1 line with the total quantity. Then in a modal page, we could assort this and specify the quantity for each variant.
Indeed this would be very usefull for a lot of industries like fashion, electronics, commodities,etc..
I very much agree with this idea; It's basic to be able to define multiple attributes for a variant like size, color, configuration, etc... It's very unconvinient if for example a shirt comes in 5 colors and 5 sizes, we cannot search for colors available in one size.
Altogether, I would propose taking this much further, and change the item variant functionality for item dimensions functionality, so that when making purchase or sales orders, you could assort a line, for example, the order line has 120 pieces, and then you can assort and say 60 of variant A and 60 of variant B. Even better if variants had attributes, and we could insert quantities in a table where columns are one variant attribute and lines another one.
the pdfViewer is a remarkable and necessary feature (what you see is what you have) but in some cases it's necessary to change the destination to print it in another format.
I have to agree with Mikael Thusgaard Johansson, and it would be really nice feature to support more then 2 dimensions to be posted in GL Entry and all linked tables,but we should agree on number of dimensions here.
What do you mean by 3-8? If setup has only 4 dimensions should only 4 be posted then, and what about 5-8 dimensions? Sure, values can be posted as blanks, but that would then mean to support all 8 dimensions everywhere in any table, etc.
We should say that out-of-the-box there should be 8 dimensions required per company.
Frankly, I have dealt with customers that used at least 8 dimensions (the UK, Holland, Germany, Adriatic Region).