Object And Field picklist updates #1549
Conversation
…imneted master label on template Removed testproperty Removed fieldList check from for loop Updated fieldList to support multiple inputs when allowFieldMultiselect is true Implemented master label section
|
I don't think that should impact it the fields and objects should be
returned from the controller the API version of the controller should be
what the results are but I think we will want to update component APIs
going forward though based on the latest release notes I think API version
will start having and impact on lightning component updates.
…On Thu, Jun 20, 2024, 1:32 PM Eric Smith ***@***.***> wrote:
***@***.**** commented on this pull request.
Does leaving the API version at 46.0 mean that newer objects are
unavailable to the component?
—
Reply to this email directly, view it on GitHub
<#1549 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMRS7YTZIAYSOJJEY75KDY3ZIM37HAVCNFSM6AAAAABJUUOSQ2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCMZRGMYDANBQGY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
|
Is it safe for me to update the API version to 61 because the Summer '24 deployment is ongoing?
|
|
Also I see another component ObjectAndFieldPickerFSC that is outside of the FlowScreenComponentsBasePack does that need to be in sync with the base pack version?
|
Change API Version from 46 to 60
|
@jdayment and @ericrsmith35 I updated the API version to 60.0 on this component |
|
StreckerCM, thanks for these enhancements! We don't get such careful scrutiny of the screen code very often, and I relly value it. I'm pretty sure that the component with FSC on the end is obsolete. All the modern components that go into the screen components base pack start with 'fsc_' so you can ignore the ObjectAndFieldPickerFSC. @jdayment can you code review this? |
Updated field property to support multiple fields when allowFieldMultiselect is true
Implemented masterLabel property on the HTML template. This property was captured but was not implemented on the template.
Removed the property testproperty because it was not used anywhere and looked to be remnant of debugging.
Updated the field property to allow multiple selected fields to be passed into the component when allowFieldMultiselect is true.
There is a check to see if the fields in the property field is available on the selected object. This check existed in the loop that got all the objects field. It did not use any of the variables from the loop. If the pass field did not exist on the object the property would be cleared, and the check would only occur on the first loop. However, if the field is part of the selected object this check would occur on each loop. I moved this check outside of the loop prior to the start of the loop.