cdevelin

Results 7 comments of cdevelin

FlowScreenComponentsBasePack-Draw a Line-Screen Crash after clicking Previous

![IMG_0155](https://github.com/alexed1/LightningFlowComponents/assets/92626240/2b2048f1-e285-4f80-898b-36dd56fbfe36) ![IMG_0154](https://github.com/alexed1/LightningFlowComponents/assets/92626240/5785d2e3-7d99-40ae-9b83-37229cb91f5d)

FlowScreenComponentsBasePack-Draw a Line-Screen Crash after clicking Previous

If it is an underlying SF bug, the scratch org I am testing with is on CS58, which is patch level: Summer '23 Patch 14.3

Latest 2GP Packaging Engine throws error with Apex Rollup: "RollupFullRecalcProcessor : Managed type that is released without a supertype can not subsequently extend another type"

Thanks James, case number is 470764963

Latest 2GP Packaging Engine throws error with Apex Rollup: "RollupFullRecalcProcessor : Managed type that is released without a supertype can not subsequently extend another type"

@jamessimone SF support have not made any progress on this error arising from the update to their packaging engine (I understand it was overhauled to support the new upgrade path...

Latest 2GP Packaging Engine throws error with Apex Rollup: "RollupFullRecalcProcessor : Managed type that is released without a supertype can not subsequently extend another type"

Hi @jamessimone This Supertype issue is still unresolved in Salesforce’s packaging process. We tried breaking ancestry and creating a fresh package which includes Apex Rollup, but has no ancestors; packaged...

Latest 2GP Packaging Engine throws error with Apex Rollup: "RollupFullRecalcProcessor : Managed type that is released without a supertype can not subsequently extend another type"

> [@cdevelin](https://github.com/cdevelin) we have just started to hit the same error when trying to create a new version of our 2GP managed package. Did you get any feedback from Salesforce...

Flow Invocable Action "Full Recalc Comma-Separated Parent API Names" works in debug mode but fails when scheduled

Update: I just tried scheduling it for a SINGLE hard-coded parent record, and it worked. I presume this indicates incorrect bulkification in responding to Salesforce batching multiple records when calling...