on
RE:
Hi, following up with others here. The main issue from Microsoft's side is that this framework is built on DLLs which means building a API to communicate with this external solution is probably not an easy task to accomplish. One other issue is that the framework requires a order line reference to complete the configuration. This means that the API would then have to get called against or generate the order line in the same operation, which is not always possible if the order is created in one transaction scope. Based on this a "general" API to solve the configuration seems like a hard task to complete.In my current project we've built an integration solution that runs during sales order creation and accepts configuration attribute values from an external source and maps it to several product configuration models through XML parsing. The code handles configuration on several models even though only one is associated to the sales order line. This however requires the reference being set to the sales order line for all configurated items even though they are configured attached from the main component (not utilizing the sub-component relation). It's not a pretty solution but is works. Why this is important to keep pushing is for Microsoft to actually put some effort in improving the solution and hopefully making it easier to use in code rather than doing XML parsing to solve the case. This is broadly used by customers and many rely on this framework. A framework that is this important should be easier to implement and improve.
RE:
Hi Vanessa, good idea !
RE:
Last remark where it says "step 4c" should be "step 7" (the indent in the text editor is not working here)
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.