2,645
Hello,
I need to auto populate 2 fields. Field B should be populated with the current user logged into CRM. Field C should be auto populated with the current Date.
Both Field B and C should only be populated once Field A is either answered Yes or No. If it is blank the 2 fields shouldn't be populated.
Any help is appreciated.
*This post is locked for comments
I was able to get the workflow working based on what you guys said. I used the modified on and modified by to be placed into my 2 fields that I created. The issue that I was having is that I just wasn't giving the workflow time to run before going back into the record as I didn't see the information being populated. When I gave it a second or just hit F5, the information updated correctly.
Thank you both.
Oh, I don't think it's a "workflow approach" issue - there is something else. I don't know what it is, but, like I said above, workflow works fine in my environment (365 online) with both "create" and "update".
So, based on this...
I think that you have three choices:
1- Go back to the JavaScript route, and add the onChange event to the Approved field.
2- Try to see if you can get this working using Business Rules. Set a rule for value of Yes/No
3- If there are any fields on the form that have to be populated, before the approved field does, you can trigger a save event. This will cause the workflow that you have now work on new records, since they become existing.
Do any of these choices work for you?
That's exactly what I meant.
I think that was is happening is that he is making the change to the attribute before the record is saved, and expecting the onChange event to execute.
Hi Aric.. Should be something else there.. You can register a real-time workflow oncreate and it will run just fine (onchange won't run, though, that's correct.. same thing with the create/update plugins)
I might be wrong regarding this, but AFAIK real time workflow will not execute on change on a record that has not yet been saved (new record). Alex?
In that case, you can force a save (JavaScript) before the user clicks on the Approved field, or the other option is use JavaScript on the change event as we discussed earlier...
There might be another option of using Business Rules on the change the approved field.
Well.. it does work for me on create - just tried.
As for not doing that when there is no data in the field, just add a condition and stop the workflow when the field is empty. Or create two workflows if needed - one for oncreate, another one of onupdate.. It depends on what other logic you want to have there (for example, what if somebody removes any value from that field? Do you still want to update the date/user field when that happens? Add conditions to the workflow as needed)
I don't want these fields populated when the record is created if the Approved field isn't changed. I did though try and check the "Record is created" under the Start when:, but that didn't work either.
So really the 2 fields need to update only when the Approved field has been changed. If someone comes into the record and changes a different record, then those 2 fields shouldn't get updated. Hope that makes sense.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (