SBX - Search With Button

SBX - Forum Post Title

Hide (Active for X hours) information from Business Process Flow

Microsoft Dynamics CRM Forum

Cathy_CRM asked a question on 1 Oct 2018 11:04 PM

Question Status

Verified

Hello,

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!

Thank you!

Regards.

Cathy. 

Reply
Wei Jie Fun responded on 1 Oct 2018 11:06 PM
Verified Answer

Hi,

Unfortunately , there is not supported way to hide this information.

Reply
Cathy_CRM responded on 1 Oct 2018 11:08 PM

Yes that's what I figured too! So is the "unsupported" way "modifying" the DOM? Or do you mean any other unsupported way?

Reply
Wei Jie Fun responded on 1 Oct 2018 11:10 PM
Verified Answer

Hi,

yes , if you insist to hide it, you have to modify the DOM.

Reply
Cathy_CRM responded on 1 Oct 2018 11:13 PM

Yes that's what I thought too! Modifying the DOM unfortunately is not supported, so I don't want to go that route either! :(

Reply
Wei Jie Fun responded on 1 Oct 2018 11:19 PM

Hi,

so, tell your client there is no supported way to hide it. Just live with it. :)

Reply
Cathy_CRM responded on 2 Oct 2018 12:38 AM

Hey,

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! :)

Reply
Wei Jie Fun responded on 2 Oct 2018 12:41 AM
Suggested Answer

Hi,

Please also stated the consequences of using DOM. I believe they will not consider it after that.

Reply
Cathy_CRM responded on 2 Oct 2018 1:02 AM

Hey,

Which consequences do you want me to primarily highlight and state to them? Please let me know.

Regards,

Cathy.

Reply
Wei Jie Fun responded on 2 Oct 2018 1:17 AM
Suggested Answer

Hi,

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.

gonzaloruizcrm.blogspot.com/.../risks-of-unsupported-customizations-in.html

Reply
Cathy_CRM responded on 4 Oct 2018 1:44 AM

Hello Fun,

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.

Reply
Wei Jie Fun responded on 4 Oct 2018 4:35 AM
Suggested Answer

Hi,

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.

Reply
Ravi Kashyap responded on 4 Oct 2018 5:41 AM
Suggested Answer

Hi Cathy,

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 :)

https://admin.dynamics.com

Hope this helps.

Reply
Wei Jie Fun responded on 1 Oct 2018 11:06 PM
Verified Answer

Hi,

Unfortunately , there is not supported way to hide this information.

Reply
Wei Jie Fun responded on 1 Oct 2018 11:10 PM
Verified Answer

Hi,

yes , if you insist to hide it, you have to modify the DOM.

Reply
Wei Jie Fun responded on 2 Oct 2018 12:41 AM
Suggested Answer

Hi,

Please also stated the consequences of using DOM. I believe they will not consider it after that.

Reply
Wei Jie Fun responded on 2 Oct 2018 1:17 AM
Suggested Answer

Hi,

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.

gonzaloruizcrm.blogspot.com/.../risks-of-unsupported-customizations-in.html

Reply
Wei Jie Fun responded on 4 Oct 2018 4:35 AM
Suggested Answer

Hi,

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.

Reply
Ravi Kashyap responded on 4 Oct 2018 5:41 AM
Suggested Answer

Hi Cathy,

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 :)

https://admin.dynamics.com

Hope this helps.

Reply

SBX - Two Col Forum

SBX - Migrated JS