on
RE:
Link to further explanation & Microsoft ticket:https://www.yammer.com/dynamicsaxfeedbackprograms/threads/3192888460910592
RE:
Hey Benjamin,I voted for your CR - please also have a look at this one:Enable (global) Personalization (Placeholders) in Senders entity and create an aditional "Name" fieldhttps://experience.dynamics.com/ideas/idea/?ideaid=dcb92768-bdf9-ef11-a4dd-6045bd85824d#BRFerdinand
RE:
We had a similar problem in January 2025.We created an MS ticket for it and “one day” it should be fixed...Feedback from MS-Support:Symptom:The incident involves issues with email templates in the Premier service, where users are unable to load, delete, or edit templates effectively. The problems manifest particularly when users have a large number of templates, leading to missing functionalities such as the edit button and difficulties in selecting or unselecting records. Users reported that the edit button disappears when selecting certain email templates, and active email templates are not loading properly.Resolution: We have reviewed the issue with the customer and escalated to our Engineering team and they have finished investigating the issues and created a work item/bug for them that will be addressed to track and fix issues on gallery side 4568634, however we didn't change anything on the Gallery side.We would like to share that we will address them in the upcoming release. For now, customers can delete a template by opening the entity and using the ribbon of the record.Regarding this Work items may take time to fix, and everything happens, and delays are possible, as a work item is created, it is on Engineering side now, you can contact me once a month if needed here or teams to request update for it.I appreciate once more your collaboration and understanding regarding this!
RE:
I forgot to explain the whish "...and create an aditional "name"-field. At the moment the senders name field is used as the entity record name. WIll not work with "placeholders" - Therefore, I would like to have a new field for the “sender name” or the name of the entity record.
RE:
This is an excellent suggestion!
RE:
Disappointed to find this is still a gap after so long, and with the move to RT forms. We desperately need conditional logic on the forms (and a low code option to configure prefilling from query string parameters). In the HE sector customers are forced to have to use Gecko forms or another 3rd party forms engine like Jotform with Power Automate integration. Power Pages with conditional logic on forms using Javascript is not feasible as business users need to be able to update these forms regularly. Please prioritise this feature :)
RE:
+ If not a batch it could instead be an automatic validation if last validation has exceed XXX days
RE:
Hi, tax groups are very important and urgently needed!Moreover I would like to point that regular payment normally (in many countries) means receiving purchase invoice. In practice it means:a) tax transactionb) other costsc) invoice may concern many lease agreements and lease assetsd) invoice may come from internal workflow (with other tipical invoices)e) etc.Having all above in mind creating lease journal via payment schedule seems to be not sufficient. Please consider ability of posting leasing invoices through invoice journal, pending invoices etc. with ability of selecting lease agreement in the invoice line (similar to posting fixed assets) or at least lease journal should be editable as mentioned in idea: Asset Leasing - Add and Edit lines in asset leasing journalThanks
RE:
HiIt's the same when you take the data directly from a trigger for a number. Which is qute a pity because we are using trigger for an esahop abandoned cart scenario and there a lot of the prices have a decimal value. It should also be considered
RE:
can't see in "What's new and planned for Dynamics 365 Supply Chain Management"