Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOQL Datatable - Output selected recordIds in its own output #61

Closed
solo-1234 opened this issue Jan 25, 2021 · 7 comments
Closed

SOQL Datatable - Output selected recordIds in its own output #61

solo-1234 opened this issue Jan 25, 2021 · 7 comments
Labels
wontfix This will not be worked on

Comments

@solo-1234
Copy link
Contributor

solo-1234 commented Jan 25, 2021

I have a soql datatable on a record page which has a button that calls a flow and passes in the selected records. Since fields from parent records aren't included during the handoff, I'm going to run my own query inside the flow to fetch them. What do you think about passing in a text-collection of record ids in addition to the record collection? That would save a step (extracting their Ids from the collection) in my flow.

@tsalb
Copy link
Owner

tsalb commented Jan 25, 2021

Related to #45 under the general request of "more output types".

I am not sure where I want to go with this yet because it can be a slippery slope - add more of these parsing features inside my lib OR wait until the platform matures to be able to extract them from flow more natively.

I am leaning on the latter but stay tuned for further updates!

@tsalb tsalb changed the title SOQLDatatable on Flexipage - Flow Action - pass a collection of record ids for selected records SOQL Datatable - Output selected recordIds in its own output Jan 25, 2021
@tsalb tsalb added the enhancement New feature or request label Jan 25, 2021
@solo-1234
Copy link
Contributor Author

Right I hear that!

Another idea along the same lines would be if flows were not required to create all the input vars that the datatable can send; instead allow the admin to create vars for whichever pieces of information they will need in the flow.

I don't know what technical limitations are involved in that but it would be a nice enhancement if not a big deal.

@tsalb
Copy link
Owner

tsalb commented Jan 26, 2021

Another idea along the same lines would be if flows were not required to create all the input vars that the datatable can send; instead allow the admin to create vars for whichever pieces of information they will need in the flow.

This is probably easier solved in the FAQ / WIKI for the moment

@solo-1234
Copy link
Contributor Author

Short term: definitely
Long term: you may want to consider actually making them optional. I just created a new flow to be used as a table action and ended up cloning an old one to save all the work of creating those four input vars.

@tsalb
Copy link
Owner

tsalb commented Jan 27, 2021

@solo-1234 for this piece, I would recommend creating a template that has all 4 variables that are required.

Due to the way I am handing it off, it is much easier to recommend to everyone always create these variables as to only sometimes create these variables. As of right now, I don't believe it is (easily) technically feasible to determine if the component is currently being used inside flow or on a flexipage.

Additionally, I don't want to introduce code bloat for checking that (just yet).

I'd say this is off topic for this specific FR though - if you'd like to submit another issue around this let's continue conversation in another issue!

@tsalb
Copy link
Owner

tsalb commented Jan 27, 2021

Closing this as duplicate in the above issue

@tsalb tsalb closed this as completed Jan 27, 2021
@tsalb tsalb added wontfix This will not be worked on and removed enhancement New feature or request labels Jan 27, 2021
@solo-1234
Copy link
Contributor Author

good idea!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants