Hi, I am getting error in the formula field of missing parathesis, IF(TEXT({!$Record.Type__c}) = "LCD_RT", "012Hr000000R28PIAS" IF(TEXT({!$Record.Type__c})= "LED_RT", "012Hr000000R28UIAS" IF(TEXT({!$Record.Type__c})= "Plasma_RT", "012Hr000000R28KIAS" {!$Record.RecordTypeId} ))) Where have i missed them??
@user-uz3hj7hz7r
Жыл бұрын
Build an automation for creating interview records???? Upload a video related to this module in trailhead...
@shahidafrid526
2 жыл бұрын
Is there way we can make web to case form dynamic. Based on radio button selection?
@salesforceatlas
2 жыл бұрын
Hi Shahid! Are you using Experience Cloud? If yes, you could create a screen flow for forms and then yes you could use radio buttons
@shahidafrid526
2 жыл бұрын
@@salesforceatlas thank you so much 😊 you always give better answer 👍 Not experienced but will try referring videos Thank you once again
@vinaya7759
Жыл бұрын
Hey Hi , Am trying to update the record before saving the record, unfortunately it is not updating. How to do it upon changing the picklist is changed option? kindly let me know. and thank you for this video.
@salesforceatlas
Жыл бұрын
Hi Vinay! Yes it's a tricky one. To work around this issue, you can use a "Record Lookup" element in your Flow to retrieve the current values of the record you want to update, and then compare those values to the new values in the Flow. If the values are different, you can update the record, and if they are the same, you can skip the update. Try this: Add a "Record Lookup" element to your Flow and configure it to retrieve the current values of the record you want to update. Add an "Assignment" element to your Flow and use it to compare the values of the field you want to check for changes. You can use a formula to compare the old value with the new value. Add a decision element to check the result of the comparison. If the values are the same, skip the update. If the values are different, update the record using the "Update Records" element.
@salesforceatlas
Жыл бұрын
your issue occurs because the "IsChanged" condition in the Flow is evaluated after the record is saved, which means that any changes made by the Flow are not considered when evaluating the condition.
@vinaya7759
Жыл бұрын
@@salesforceatlas Thank you very much for your reply and this video helped a lot. I look forward for more videos. If you don't mind I would like to connect with you in LinkedIn or google hangouts. Kindly share your id.
@amandeepsinghandheri4546
Жыл бұрын
Did you create Account Record Type on Account object first before creating the Flow?
@salesforceatlas
Жыл бұрын
Hi Amandeep, I didn't create account record type specifically for this video but yes they're were already in the org so definitely before the flow.
@amandeepsinghandheri4546
Жыл бұрын
@@salesforceatlas Sorry I meant Account Record Type Field. How is it, that the Account Record Type field was already present on the Account Page Layout? Did you create a new field on the Account Object or does it appear automatically through this process?
@salesforceatlas
Жыл бұрын
@Amandeep Singh Andheri oh yes, it came out of the box with the playground as a standard field
@montecrucis7247
Жыл бұрын
Account Type is not the same as Account Record Type.
@salesforceatlas
Жыл бұрын
Hi Monte, yes agree. Sorry if I mentioned that its the same. In the video, I focused on the record type.
Пікірлер: 23