Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
What is the easiest way to Hide (Active for X hours) information from the Business Process Flow for any entity. I don't need the user to see any information in the parenthesis. Just need to show them, the Stage Values like Received, Investigation, Closed etc.
Here is the screenshot below[in this I need to remove/hide the :- "(Active for 12 hours)"]
Any help would be really appreciated!
Unfortunately , there is not supported way to hide this information.
Yes that's what I figured too! So is the "unsupported" way "modifying" the DOM? Or do you mean any other unsupported way?
yes , if you insist to hide it, you have to modify the DOM.
Yes that's what I thought too! Modifying the DOM unfortunately is not supported, so I don't want to go that route either! :(
so, tell your client there is no supported way to hide it. Just live with it. :)
Yep! I have already told them last week regarding no supported methods besides DOM modification(which is unsupported), but I will confirm the same to them this week as well! :)
Please also stated the consequences of using DOM. I believe they will not consider it after that.
Which consequences do you want me to primarily highlight and state to them? Please let me know.
You can shared about, by using DOM,
1. Microsoft is not going to support if anything goes wrong because of using unsupported code.
2. This might not work in future because of future updates, they have to spend money to fix it (unsupported method again), It is a vicious circle.
3. Not everyone knows how to fix it.
you can share below blog to your client.
I know the drawbacks of "unsupported code" in general, even the link only talks about risks of unsupported code, which are all known risks to me. I thought you were going to talk about the consequences of using DOM and why modifying the DOM itself is not a good idea.
ya, those are the consequences of using" unsupported method".
eg, currently the control name is "control1" , Maybe in future release update, Microsoft changed it to "MS_control1", which related to second point i mentioned earlier.
You could contact Microsoft and ask them to confirm if there is any supported way and then when MS respond that there isn't any supported way, you can share the confirmation to your client. The email confirmation from Microsoft worked for me in the past to convince clients :)
Hope this helps.
Business Applications communities