MAS doesn't seem to kick off action about sfdx-mass-action-scheduler HOT 6 CLOSED

Thank you! I'm excited about the new release.

As so often happens with such complex requests, the person requesting it changed his mind after I did this work, and so I haven't pursued the issue. I'm going to close this - MAS continues to work perfectly for me in many situations!

from sfdx-mass-action-scheduler.

Hi Anna, glad to hear you’re getting good use out of Mass Action Scheduler.

For this opportunity quick action, would you please share screen shots of the action’s field layout and where you’ve defined the default values for the field update on the action, and screen shot in Mass Action Configuration wizard of the field mapping step?

Thanks

from sfdx-mass-action-scheduler.

Hi Doug,
Thanks so much for the response, especially on a weekend!

I'm including these screenshots. It is just the one predefined field for the action, and the formula is so long it won't show up in a single screen. I've just blurred the text that I'm inserting to protect the identity of the organization with a business process that would inspire such a monstrosity. ;-)

from sfdx-mass-action-scheduler.

Hi @annacrotty,

I did a test and I was able to perform a field update on Account record using a "Update Record" quick action using predefined field value using IF formula and no fields on the layout. In my test, the record was updated accordingly (screen shot below).

For troubleshooting, in order of simplest to do to a bit more effort, please try:

1. Confirm that the Mass Action record is Active. It probably is based on your comments, but if it were inactive that would definitely be a cause for the record not updating.

2. Simplify the formula to something very trivial, perhaps a static value like "test", to confirm that the Mass Action updates the record. If it does with the simplified formula, then the issue may be with the formula -- and perhaps not a problem but perhaps it's resolving to a different value than what you're expecting.

3. Check that there aren't other triggers/processes/workflow rules/etc running that may be modifying the field. I bring this up because in my org I did have a process builder overwriting the field I was testing (I have bad habit of always updating the Account.Description field so high chances of conflicts).

from sfdx-mass-action-scheduler.

Hi @annacrotty, Release 2.0 is now available. You can install it from here.

Kindly try out the new version and see if that resolves your issue. This new release does not require Named Credentials anymore, and if that was the issue, then the problem should be gone.

Thanks!

from sfdx-mass-action-scheduler.

Glad to hear both the complex request went away (hopefully 😉) and that MAS is still working out well for you.

from sfdx-mass-action-scheduler.