-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add the ability to select an existing CMDT record when recalculating #59
Comments
Follow-up thought on this - I initially wrote that the list of |
Yeah, I think that's a great idea. We can just group the |
Was just coming over to log this specific issue. I built 4 rollups from the same |
@dhoechst excellent feedback to add into the mix. I’m planning to knock this one out this weekend! |
…ings Introduced (#61) * Fixes #59 by adding CMDT section to the Rollup recalculation application * Fixes #58 by adding Rollup Settings hierarchy custom setting for granular user, profile, and org-wide rollup control - plus it will make installing/upgrading a whole lot easier * @jongpie feedback (w h i t e s p a c e on the 'Id' field), added note in Readme about screen locking for full recalculation, added first jest unit test for rollupForceRecalculation LWC * fixing Github Action * Finishing initial round of jest testing for rollupForceRecalculation LWC * Updating build script to be less strict if removing scratch org is the failure reason * Last of @jongpie feedback - defaulting RollupSettings__c.IsEnabled__c to true
The "Recalculate Rollup" component currently requires you to enter all of the rollup details. This works great with having full control - but if you've already defined a
Rollup__mdt
record with all of the details, it's a little repetitive to have to re-enter it. Ideally, this component should have 2 options to select fromEntityDefinition
fieldsRollup__mdt
records (maybe displayed in a dropdown?) for the admin/user to selectIn either scenario, I think you'd still want to be able to specify a
WHERE
clause, so the existing input "Where Clause SOQL Filters (Optional)" should be displayed for both options.The text was updated successfully, but these errors were encountered: