Update documentation to reflect use in new Lightning Professional Edition

[m-a-t-m]

It is now possible to install the managed package in a Lightning Professional Edition and configure entries to trigger Process Builder to action the declarative roll up summary.

[afawcett]

Yes! Yes! Yes! 👍

[JimBTek]

added to wiki page but not readme

[afawcett]

Thanks @JimBTek 👍

[matti-sch]

Great thing that your amazing tool now is available also for Professional Editions.

I can't figure how to do it, however.

1. First of all, I am not able to deploy the code for the child trigger. But that might be the thing that is not possible to do in PE?
2. I have selected Calculation mode = Process Builder. But do I need to do anything else? Create some kind of process in Process Builder?

If you just point me in the right direction I would, after succeeding, be happy to update the Wiki to help other lost souls.

[afawcett]

RE: 1, you cannot do this in PE and you don't need to if your using Process Builder.

RE: 2, yes you need to create Process Builder as defined in this blog here, make sure the rollup is marked as Active.

[afawcett]

README updated.

[faceroy]

Hi Andy,

Followed the blog post (in relation to utilising in a PE org) but unable to see the call Apex option for actions.

Any ideas?

Thanks in advance

[afawcett]

That is odd, can you send a screenshot?

[faceroy]

Sure, here you go... Thanks for your assistance.

[afawcett]

Thats really odd, your missing the Apex Action action type? I have never seen that before. . I wonder if there is some restriction in PE orgs? If so, i wonder how i have ever got reports of DLRS working in PE tbh? The documentation seems to suggest it is fine in PE though....

This is what i see, though this is in a DE org...

I did some searching, not 100% sure, but wondering if its this known issue??? The above documentation link also notes this... "If you define an Apex action in your process and then modify the Apex class by adding a standard field reference (for example, User.Phone), the Apex action is no longer visible in the process and must be added again."

Clearly though you are not writing an invocable method or for that matter changing it.... So it does not 100% add up to me yet. I also see from your screenshot your missing a few other options. I think its worth asking Salesforce support why your missing this feature. Does it occur when you create a brand new process as well btw?

[afawcett]

Check out the continued discussion on https://github.com/afawcett/declarative-lookup-rollup-summaries/issues/478...

[matti-sch]

@m-a-t-m, could you explain how you got this to work PE (even if in Lightning)? Would be really appreciated.

[m-a-t-m]

12 months ago, in May 2016 I did configure a PE org using DLRS and Process Builder with the Apex invokable action. Then it stopped working. I tracked the cause in my org to the following known issue (WHICH IS STILL OPEN 12 MONTHS LATER!?)
https://success.salesforce.com/issues_view?id=a1p300000008ZFDAA2&title=process-builder-apex-action-disappears-when-apex-class-is-modified-to-include-reference-to-some-standard-fields Could this be the issue for you too @matti-sch ?

[matti-sch]

It sure sounds like it. Thank you for sharing.

Den 25 apr. 2017 8:28 em skrev "m-a-t-m" notifications@github.com:

12 months ago, in May 2016 I did configure a PE org using DLRS and Process Builder with the Apex invokable action. Then it stopped working. I tracked the cause in my org to the following known issue (WHICH IS STILL OPEN 12 MONTHS LATER!?) https://success.salesforce.com/issues_view?id=a1p300000008ZFDAA2&title= process-builder-apex-action-disappears-when-apex-class-is- modified-to-include-reference-to-some-standard-fields Could this be the issue for you too @matti-sch https://github.com/matti-sch ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/afawcett/declarative-lookup-rollup-summaries/issues/341#issuecomment-297122717, or mute the thread https://github.com/notifications/unsubscribe-auth/AM6GoopC_SysZ4lqaYVICvgTQBH-YUggks5rzjswgaJpZM4Il5pG .

[m-a-t-m]

Is it possible to work around the known issue @afawcett by removing references to the standard fields inside DLRS classes? I am guessing probably not, you wouldn't have them in there if they were not needed.

[chadwix]

For the benefit of posterity, we're a SF Lightning Professional Edition organization and were seeking to sum a field from child Accounts to each Parent Account (which are territories, the way we use SF).

To get this to work -- which it does wonderfully -- we followed the installation instructions here (although the version that article links to is outdated), then did the following:

• Left "Active" unselected when we first created the Rollup
• Set Calculation Mode to "Process Builder"
• Once we'd saved the Rollup, we went back and selected "Active", then resaved
• We tried clicking "Manage Child Trigger" (accessed by clicking the top-right menu arrow next to the Action Buttons). When we did this, SF threw an error.
• On a whim, we clicked the "Calculate" action just above the "Manage Child Trigger" action, and the Rollup worked.

Not that, although we built a Process in Process Builder, we tested out what would happen if we deactivated it, and the Rollup continued to work and recalculate as we expected when we ran some tests.

Hope this helps anyone in the future.