on
RE:
Your IT Administration can add any application to App Launcher - https://learn.microsoft.com/en-us/microsoft-365/admin/manage/pin-apps-to-app-launcher?view=o365-worldwide
RE:
I would also like to request allowing breadcrums to be clickable. I brought it back as suggested, but this should be a permanent solution and it should be clickable. Let your customers decide, please, what navigation and user experience works for them.
RE:
Currently, I use Variables to accomplish this and then use logic branching to ask if the Variable in question is correct, and then if not, they can correct on a subsequent question, or the question is skipped if they indicate it is correct.It says you can also save the variables, but I haven't fully tested this out - trying to determine if that will save it in an easier location when using Power Automate flows, than having to grab all the questions from the survey and filtering to find the values that you want so that you can update Contact records fields beyond just the name and email.Having only 15 variables is a HUGE limitation, especially since First Name, Last, Name and Email are necessary and that leaves me with only 12 other variables. I need like 24 or 25 for one particular survey. The end-user UX is a bit clunky with this logic, but it gets the jobs done, mostly.
RE:
It would also be nice if there was a W-9 Expiration Date Field on the Vendor card that could be filled in so a report can be run on expiring W-9s,
RE:
I'm fully in agreement with Sunil's proposed idea and Ismail's comment. One client I worked with that has predominately cost-type invoices considered the Invoice Capture App but ultimately decided to go the direction of an ISV. One of the reasons they made that decision was this described issue.
RE:
From all the discussion with Microsoft. I think the only think we will ever get is to download your own extensions.Microsoft will never want to pass your IP to somebody else. But it would still be great If I would download runtimes for our own apps if a customer requests it. But a OnPrem AppSource Integration will never happen.We are currently using Github Runners to create runtimes automaticly but that takes around 11 hours per release per app. Not quite efficent. Because Microsoft will do the same after I've released to AppSource again.
RE:
The order date for a planned purchase must also consider the Vendor purchase calendar, we're waiting for this solution.
RE:
Still ridiculous that this isn't a standard feature
RE:
I totally agree with your proposal to group all cost invoices into a single journal with each treated as a separate voucher. This approach will indeed reduce the number of records and improve navigation and searchability within the invoice journal grid. Additionally, attaching relevant documents at the voucher level will enhance accessibility and streamline the process. I believe this change will greatly improve our efficiency and user experience with D365 Finance. Looking forward to implementing this solution.
RE:
I would suggest custom Styles at the least! The existings Styles were bad enough, but the colors are getting worse and worse with each version! Blue !? Yellow ?! In the past... now it's also just grayish...blueish.. brownish...Realisticly I would suggest: Font/FontSize/ForgroundColor/BackGroundColor! That should be easily feasable.Best would be custom css, but I can see where this might lead to complications. But better an unsupported feature than being stuck with 3 colors (Normal, Red Bold, Green Bold = all others are simply not differentiable).Background-Color is even more important than foreground-color! I need to highlight rows all the time... but simply have to fake it...