Feed

I found better solution now :  

When u add utility Items on Utility bar Label is required field but you can add Zero Width Space character.    Copy it from this link :

.     

paste  it in label field. This will not be visible to end user. 

Do not  select icon which is optional anyway. 

keep Panel width, height minimum &  

Now this LWC is hidden on Utility bar, it will still clickable but apparently not visible 

I don't know where to find more information about derived measures and dimensions - but consider it to be mainly useful when you create (derive) new dimensions or measures in a SAQL statement.

Let's say you calculate a winrate in SAQL in several places of your dashboard, so it's not part of the dataset itself. If you want to make sure that the winrate is always displayed as %, you can add a derived measures with name winrate and assign the number format for percentage - as soon as the name of the derived measures matches the projection name of the measure in SAQL, the number format will be applied.

Same is for derived dimensions, where you could assign colors to given values. Unfortunately, the creation of the values (called members) has to be done in a json editor - the UI to do this is still missing.

@André Denzler

Hi André, 

Yes, you are correct, you should not expose Lead Status in your Form. The Status Field may actually be mandatory in the Create Record activity. That being said, its value does not have to come from the Form, so you may simply set it in the Flow with the value you wish. 

Hope this helps 😎 

François. 

PS : In order other Trailblazers to be pointed directly the correct answer, please do not forget to click “Accept this answer” below the correct one.

Hi @Giancarlo Amati

- I have done same kind of automation last year for one of our accounts. For this you need to simply write a trigger on ContentDocumentLink object - because this object is acting as a junction between your contentDocument(File) and any other Object (LinkedEnitity) like case or account via LinkedEntityId field. 

You need to first filter out the contentDocumentLink record which is incoming from Chat (you can make use of LinkedEntityId here as it will be of MessagingSession recordId) and then you just need to insert 2 new ContentDocumentLink record adding LinkedEntityId for Case and Account (you can get Case Id and Account Id from MessagingSession record). 

This way you can easily link the same File with MessagingSession, Case and Account records. This is tried and test approach. Hope this will solve your problem. 

Also, you can try for Flow if you want to go via No code approach. I like pro code approach coz it gives more flexibility so I went with trigger approach.  

Also, not sure if we can write a record triggered flow on ContentDocumentLink Object. I'll leave that POC for you :) 

Hope this solves your problem. Thanks!