Skip to content
This repository has been archived by the owner on May 12, 2023. It is now read-only.

Add New Source Type: Apex #4

Closed
douglascayers opened this issue Jan 2, 2018 · 1 comment
Closed

Add New Source Type: Apex #4

douglascayers opened this issue Jan 2, 2018 · 1 comment
Assignees
Labels
enhancement ✨ A new feature suggestion or improvement upon an existing feature. source: apex Related to getting source records to process from Apex code. status: resolved ✅ This has been addressed in a branch and will be scheduled for release in the assigned milestone.
Milestone

Comments

@douglascayers
Copy link
Member

Allow developers to implement an interface that returns the records to iterate over. This may be necessary when the criteria of what records to process cannot be expressed in a report, list view, or literal SOQL query. For example, if custom settings, metadata, or other business logic is needed to identify the records.

@douglascayers douglascayers added the enhancement ✨ A new feature suggestion or improvement upon an existing feature. label Jan 2, 2018
@douglascayers douglascayers self-assigned this Jan 2, 2018
@douglascayers douglascayers changed the title Source Type: Apex Add New Source Type: Apex Jan 2, 2018
@douglascayers douglascayers added feature enhancement ✨ A new feature suggestion or improvement upon an existing feature. and removed enhancement ✨ A new feature suggestion or improvement upon an existing feature. feature labels Jan 3, 2019
@douglascayers douglascayers added this to the Release 2.1 milestone Jan 6, 2019
@douglascayers douglascayers added the status: in progress ❇️ Currently being developed for a future release. label Jan 6, 2019
@douglascayers
Copy link
Member Author

This is scheduled for the next build, Release 2.1

This will take advantage of the MA_IterableSourceBatchable Apex class introduced in Release 2.0 in support of the SOQL source type.

I'm thinking for the new Apex source type, I'll prompt for the name of an Apex class. That Apex class should implement Iterable<Map<String, Object>>.

What I'm not sure on yet is how the Field Mapping step will work. I prefer to provide the picklists, but I think for Apex (and probably could or should have for SOQL), need to just let the user enter plain text of the keys to pull from the Map<String, Object> provided by the custom Apex iterable.

@douglascayers douglascayers added the source: apex Related to getting source records to process from Apex code. label Jan 6, 2019
@douglascayers douglascayers added status: resolved ✅ This has been addressed in a branch and will be scheduled for release in the assigned milestone. and removed status: in progress ❇️ Currently being developed for a future release. labels Jan 28, 2019
@douglascayers douglascayers removed status: resolved ✅ This has been addressed in a branch and will be scheduled for release in the assigned milestone. labels Jun 25, 2019
@douglascayers douglascayers added the status: resolved ✅ This has been addressed in a branch and will be scheduled for release in the assigned milestone. label Jul 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement ✨ A new feature suggestion or improvement upon an existing feature. source: apex Related to getting source records to process from Apex code. status: resolved ✅ This has been addressed in a branch and will be scheduled for release in the assigned milestone.
Development

No branches or pull requests

1 participant