In an older page I have a button that ‘runs datasource action’ SFDC web link. I’m trying to add the same thing to a new page but SFDC Web Link is not visible under the datasource actions.
Did this move or any idea why it’s not showing up on my new page?
Both pages are in the same org. Version: 15.0.11
Best answer by Rob_Hatch
Anna’s proposal should work, but here is the more fundamental reality.
The list of available datasource actions is built based on the model context of the component that is firing the action. So if you button’s container is not bound to a model - we don’t know for sure what actions should be made available. And because the available SFDC WebLInks are sourced from metadata about the sObject - we need that model context in order to retrieve the availalbe webLinks. So we don’t show the SFDC WebLinks option…
So - make sure your button set (or table or page header) is tied to the model where the SFDC Weblink action is configured. And the action should be available.
I admit - we could do better here. I think we should allow weblink actions to be selectable even from a button that does not have model context - as long as you enforce setting the model in the configuration of the button. We’ll add that to the backlog.
+18s datasource action’ SFDC web link. I’m trying to add the same thing to a new page but SFDC Web Link is not visible under the datasource actions.
Did this move or any idea why it’s not sh
Hey @TWyatt, I’m not sure if something has changed on the Skuid or the Salesforce API side, but for now are you able you take the button XML from the old page and paste it into the new page?
Is the action working as expected?
+17Anna’s proposal should work, but here is the more fundamental reality.
The list of available datasource actions is built based on the model context of the component that is firing the action. So if you button’s container is not bound to a model - we don’t know for sure what actions should be made available. And because the available SFDC WebLInks are sourced from metadata about the sObject - we need that model context in order to retrieve the availalbe webLinks. So we don’t show the SFDC WebLinks option…
So - make sure your button set (or table or page header) is tied to the model where the SFDC Weblink action is configured. And the action should be available.
I admit - we could do better here. I think we should allow weblink actions to be selectable even from a button that does not have model context - as long as you enforce setting the model in the configuration of the button. We’ll add that to the backlog.
@Rob_Hatch Thanks. Setting the button model was the problem. And my team is going to start using your term “fundamental reality”. 🙂
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
