Hi Valeria,

I am a developer who was assigned to deal with this idea.

Can you please clarify what different format you mean? What are the differences between the default QR format and the format you mentioned?



Hello, we are very interested in getting the Route name in the forms: PRODROUTE + PRODROUTEJOB + PRODVIEWPROGRESS.

Can you please let me know when it will be available?


It's a necessity


Please consider implementing this since this is a risk if not changed.

If a buyer for example should only be able to create POs for one specific legal entity then there is no possibility to restrict the access to release PO in other legal entities from the form 'Release approved purchase requisitions' in standard. This means that if I am not employed in USMF or my security role is restricted I cannot even access the PO that was released to send the PO out to the vendor. Also there is a possibility that I by mistake release all purchase requisitions in all legal entities if I am not careful and you cannot revert this.


It does not work if other is added.

And it is not available for statements in Likert (matrix) questions ...

So no - not sufficient


May be this should be combined and solved with that one: Microsoft Idea (dynamics.com)?


There should be an automatic refresh/renewal of these keys, were the frequency is configurable. And the configuration should be done in the hardwareprofile in HQ.


REMARK: Example decision maker finance (a.g. accounts payable), or decision making (Executive or board), or decision making purchasing source agent (e.g. Purchasing representatives).


+1 for capturing what Henry calls 'Critical Control Points'. There are two aspects to quality needed at the PFE - quality results which will feed COA generation and measurement confirmations that operators are executing and running equipment within specifications.


@rizan Sif

i was testing this with the post entity.

You can tag. But you cannot search for tags. Why do you want to tag? To search by tags!! if we cannot search or filter by tags in a structured way, there is no point to create tags in the first place.

very nice point is is that you can make 1 post mentioning several #tags e.g. product type #Leisure #Business

and when you get to the project type record Leisure or business and have the timeline activated you will see on both ends the very same post linking the e.g. same opportunity you have added the post to.

however the post is very limited: e.g. you cannot query for text fields and NOT even regarding (!) :-(, very disappointing.

unable to add it to a dashboard or unable to export to excel in an ADF results page even as sys admin (well via XRM toolbox fetchxml but that's not a viable option for end users). even better would be to query for all objects such as opportunities, leads, contacts that have a post with product type Leisure ... from both ends from the product type or from the opportunity side or from the post side...