Conditions with 'a blank value' add new records with 'null' string

  • 2
  • Problem
  • Updated 2 years ago
  • Solved
In Millau, new rows in models with conditions that set to 'a blank value' have a 'null' string added instead of being null. This then leads to an error if the field data type is not a string. 

Model condition


New Row:
Photo of Craig Rosenbaum

Craig Rosenbaum

  • 4,970 Points 4k badge 2x thumb

Posted 2 years ago

  • 2
Photo of Stephen Sells

Stephen Sells, Alum

  • 17,326 Points 10k badge 2x thumb
Can you paste in the XML of this page so that we can explore in greater detail what you are seeing?
Photo of Craig Rosenbaum

Craig Rosenbaum

  • 4,970 Points 4k badge 2x thumb
Here is a demo page that has the same behavior:

<skuidpage unsavedchangeswarning="yes" personalizationmode="server" useviewportmeta="true" showsidebar="true" showheader="true" tabtooverride="Account">
    <models>
        <model id="Account" limit="100" query="true" createrowifnonefound="false" datasource="salesforce" sobject="Account" type="">
            <fields>
                <field id="Name"/>
                <field id="CreatedDate"/>
                <field id="ParentId"/>
                <field id="Parent.Name"/>
            </fields>
            <conditions>
                <condition type="blank" value="null" field="ParentId" fieldtargetobjects="Account" state="" operator="=" enclosevalueinquotes="false"/>
            </conditions>
            <actions/>
        </model>
    </models>
    <components>
        <pagetitle model="Account" uniqueid="sk-e2bUg-198">
            <maintitle>
                <template>{{Model.labelPlural}}</template>
            </maintitle>
            <subtitle>
                <template>Home</template>
            </subtitle>
            <actions>
                <action type="savecancel" uniqueid="sk-e2bUf-196"/>
            </actions>
        </pagetitle>
        <skootable showconditions="true" showsavecancel="false" searchmethod="server" searchbox="true" showexportbuttons="false" pagesize="10" createrecords="true" model="Account" mode="read" allowcolumnreordering="true" uniqueid="sk-e2bUz-212">
            <fields>
                <field id="Name" hideable="true" allowordering="true" uniqueid="fi-e2aBT-363"/>
                <field id="ParentId" hideable="true" uniqueid="fi-e2iMM-272" valuehalign="" type=""/>
                <field id="CreatedDate" hideable="true" allowordering="true" uniqueid="fi-e2aBT-364"/>
            </fields>
            <rowactions>
                <action type="edit"/>
                <action type="delete"/>
            </rowactions>
            <massactions usefirstitemasdefault="true">
                <action type="massupdate"/>
                <action type="massdelete"/>
            </massactions>
            <views>
                <view type="standard"/>
            </views>
        </skootable>
    </components>
    <resources>
        <labels/>
        <css/>
        <javascript/>
        <actionsequences uniqueid="sk-e2egm-241"/>
    </resources>
    <styles>
        <styleitem type="background" bgtype="none"/>
    </styles>
</skuidpage>
Photo of Gyan

Gyan

  • 1,422 Points 1k badge 2x thumb
We have also found the same issue.
Photo of Stephen Sells

Stephen Sells, Alum

  • 17,326 Points 10k badge 2x thumb
Thank you for bringing this to our attention. It appears there's an issue in how we are treating null and blank in our conditions. There is not a target date for getting this issue addressed yet but our devs are aware of it. 
Photo of Mark DeSimone

Mark DeSimone, Official Rep

  • 12,352 Points 10k badge 2x thumb
Official Response
Thank you for your patience! Skuid has fixed the issue you raised in the new 11.0.3 release which is now available on the Skuid Releases page.


As a reminder, Salesforce does NOT allow reverting back to prior versions of managed packages. Skuid always recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment. We also recommend that you update out of date themes when you upgrade. Please let us know if you continue to encounter any problems with this issue after upgrading.
 
Thanks again for alerting us of these issues!
(Edited)