2
I'm looking for suggestions as to how you might approach the following:
I have a requirement to stop users being from able to deactivate a Contact IF the contact currently has a record in Custom Entity "X"
Example -
Contact DOES has a row in the custom entity table under their name. Contact shouldn't be able to be deactivated
Contact does NOT have a row in the custom entity table under their name. Contact should be able to be deactivated
This was great! I had to adjust your suggestion a bit, but it was exactly the kind of template I was looking for, Thanks!
The reason I had to adjust is the custom entity may have multiple records associated to each contact.
I created a field that's updated by an onload function to count the number of records in the associated entity to the contact.
Then I used your suggestion, but made the condition that if the custom counting field > 0, to cancel.
Thanks again!
Hi Partner,
IF the contact currently has a record in Custom Entity "X"
The contact and custom entity have N:1 relationship? contacts are child records for the custom entity?
If so, one lookup field related to custom entity should on the contact entity.
When contact has a row in the custom entity table, the lookup should be populated with the custom entity.
Then you can create one real-time workflow to achieve your goal.
Save and active the workflow.
Test:
#1
André Arnaud de Cal...
291,642
Super User 2024 Season 2
#2
Martin Dráb
230,371
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
