Receiving error when trying to choose Action about sfdx-mass-action-scheduler HOT 21 CLOSED

Nevermind...got ahead of myself, changing the end of my named credential URL did not allow me to successfully choose an action :( Still having issues with this.

from sfdx-mass-action-scheduler.

@douglascayers I went through and re-setup the named credential and everything seems to be working great now! Thanks!

from sfdx-mass-action-scheduler.

Here's the excerpt from the error message in the picture above:

[Cannot read property 'length' of null]
highlightOptionWithText()@https://primerosystems.lightning.force.com/components/lightning/combobox.js:2:12206
Object.a.runActionOnBufferedTypedCharacters()@https://primerosystems.lightning.force.com/components/lightning-utils.js:2:1181
i()@https://primerosystems.lightning.force.com/components/lightning/combobox.js:2:2963
requestAnimationFrame()@https://primerosystems.lightning.force.com/components/lightning/combobox.js:2:3916

from sfdx-mass-action-scheduler.

On the chance I am able to choose an Action, when I proceed to "Field Mappings" I do not have the option to map:

from sfdx-mass-action-scheduler.

Solved. Apparently with Spring '18 release, api changed to v42.0. after changing my named credential URL to have v42.0 at the end instead of v41.0, mass scheduler is working for me.

from sfdx-mass-action-scheduler.

I am also experiencing the action selection box not populating.

"Error calling action "c.getInvocableActions""

from sfdx-mass-action-scheduler.

@ksaner92 @jnauman Which version of the app do you all have installed in your orgs? The current version is 1.5 as of this writing. And you probably do want to update your Named Credential URLs to v42.0.

@ksaner92 so this was working fine for you for 4 months and then one day it stopped working? Any idea what changed in your org that might be related?

Things to double-check are that the Named Credential URL includes your My Domain as displayed when in Classic and not what you see in the address bar when in Lightning Experience.

For example, your Named Credential URL should be like https://primerosystems.my.salesforce.com/services/data/v42.0 with a scopes full and refresh_token and the Callout Option "Generate Authorization Header" checked.

If still get errors, although it's annoying to do, you may want to try re-creating your Connected App, Auth. Provider, and Named Credential from scratch.

from sfdx-mass-action-scheduler.

Hi @douglascayers I currently have version 1.5 of the Mass Action Scheduler app installed. I have tried updating my Named Credential URL to v42.0 however that did not change the inability to choose an Action.

And yes, this has been working for me with no hiccups up until 3/29. As annoying as it is when troubleshooting, nothing has changed with my setup or any related objects, list views, process builders.

I do have 2 Named Credentials setup, with the following URLs https://primerosystems.com.my.salesforce.com/services/data/v41.0 and
https://primerosystems.com.my.salesforce.com/services/data/v42.0

Neither are working. I have tried completely uninstalling the app, re-installing, and re-created the Connected App, Auth. Provider, and Named Credentials from scratch 3 times with no success.

I appreciate your help!

from sfdx-mass-action-scheduler.

from sfdx-mass-action-scheduler.

@douglascayers I thought it was pretty strange too :| This is in production. My mass actions in sandbox are still working totally fine.

from sfdx-mass-action-scheduler.

Good to hear @jnauman

from sfdx-mass-action-scheduler.

I'm running into this exact same problem. I am in a sandbox and have made a named credentials with my sandboxes' domain as url. Is there a known cause and/or solution to this problem?

When I visit the url .my.salesforce.com/services/data/v42.0 I get

<Error>
<errorCode>INVALID_SESSION_ID</errorCode>
<message>Session expired or invalid</message>
</Error>
</Errors>

Is this related?

from sfdx-mass-action-scheduler.

Hi @jvlaar, you won't be able to go to the URL in your browser address bar because the REST API requires an Authorization header with your oauth access token in it. If you are able to create the Named Credential record successfully and get the Authenticated Status field to say Authenticated as [email protected] and the Named Credential URL is for the same domain as the org you're on, then the only thing I can think of is to make sure the oauth scopes are correct. You need at least refresh_token scope, and if you're having issues, probably want to also have full scope selected too.

Please share screen shots of your Connected App, Auth. Provider, and Named Credential if you don't mind.

Thanks

from sfdx-mass-action-scheduler.

@ksaner92 @jvlaar Do your Connected App and Named Credential both specify the exact same scopes of full and refresh_token? Make sure both match exactly and see if that has a difference.

from sfdx-mass-action-scheduler.

Another thing to consider per related issue #7 is check if your production orgs are using Two-Factor Authentication or require High Assurance Session. If yes, then you might try to setup your Named Credential to use an integration user that does not require that.

According to another user:

We also experienced this issue in our Production environment, while the same setup worked fine in our Sandbox. The difference for us was our System Administrator Profile in Production had Session Security Level set to High Assurance and only our corporate Single Sign-On or Two-Factor Authentication were considered High Assurance sessions. The issue was resolved by changing our Named Credentials settings to using a Profile that did not require High Assurance sessions.

from sfdx-mass-action-scheduler.

I am also unable to select a Process at the Choose Action step - I just recreated my Connected App, Auth Provider and Named Credential this morning, and I do have a couple of active invocable processes on the object I'm targeting, but no options appear in the picklist. I'm on version 1.5 of the app, am authenticating with a Sys Admin user, and we don't have 2FA enabled. I'm in a sandbox, and I've verified that the Named Credential URL is using the sandbox domain. I'm not sure what else to check in terms of troubleshooting. Any guidance would be appreciated! Thanks!

from sfdx-mass-action-scheduler.

Hi @BethHoward,

Thanks for trying out Mass Action Scheduler. At first look, your configuration appears correct.

Just to try some things, see if these values for your Connected App's callback url work, replacing YourOrgIdHere with your org's ID (e.g. 00Df6000000oOnmRJL):

• https://test.salesforce.com/services/authcallback/YourOrgIdHere/Mass_Action_Scheduler
• https://thinfim--BethDev.cs83.my.salesforce.com/services/authcallback/YourOrgIdHere/Mass_Action_Scheduler

from sfdx-mass-action-scheduler.

@BethHoward scratch my last comment, I misunderstood. You are able to create and authenticate with your Named Credential which means your Connected App and Auth. Provider should be correct.

Next time you're editing a Mass Action Configuration record, open your browser's developer tools and see if there are any red console errors being printed.

from sfdx-mass-action-scheduler.

FYI, for the next version of the app I have a new setup page that will automatically create and configure the Connected App, Auth. Provider, and Named Credential for you. I hope this eliminates most of the confusion and trouble with getting Mass Action Scheduler setup for folks.

At the moment, some unrelated apex test classes are failing which prevent me from creating the next package version. I'm waiting on this known issue to be fixed. It's currently in progress of being rolled out. Once NA59 gets fixed then I should be able to proceed with providing the next package version.

from sfdx-mass-action-scheduler.

Here's a video sneak peek of the new auth page.

from sfdx-mass-action-scheduler.

Salesforce is playing a bit of whack-a-mole. The known issue got resolved which fixed my first problem, but in doing so a new problem got introduced and so other previously passing tests are now failing. I'm still working with Salesforce Support on getting all issues fixed so I can push out new package updates. Thanks for your patience.

from sfdx-mass-action-scheduler.