*.ds.xml validOperators not applied in 14.1p

[stonebranch2]

Hi Isomorphic,

Did something change in 13.1p/14.1p that would impact overriding the valid operators in the ds.xml?

SmartClient Version: v14.1p_2025-03-03/Pro Deployment (built 2025-03-03)

I put together a sample *.ds.xml.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DataSource xmlns:fmt="WEB-INF/" ID="sandbox33" serverType="generic">
    <fields>
        <field name="id" type="text" primaryKey="true" canEdit="false">
            <title>UUID</title>
        </field>
        <field name="name" type="text">
            <title>Name</title>
            <validOperators>iEquals</validOperators>
            <validOperators>iNotEqual</validOperators>
            <validOperators>isNull</validOperators>
            <validOperators>notNull</validOperators>
            <validOperators>inSet</validOperators>
            <validOperators>notInSet</validOperators>
        </field>
        <field name="referenceName" type="text" canEdit="false">
            <title>Reference Name</title>
        </field>
        <field name="referenceId" foreignKey="sandbox33r.id" displayField="referenceName" foreignDisplayField="name" type="text">
            <title>Reference</title>
            <validOperators>iEquals</validOperators>
            <validOperators>iNotEqual</validOperators>
            <validOperators>isNull</validOperators>
            <validOperators>notNull</validOperators>
            <validOperators>inSet</validOperators>
            <validOperators>notInSet</validOperators>
        </field>
    </fields>
</DataSource>

In 12.1p, the FilterBuilder would show the operators as follows for the referenceId field.



However, here is what is happening with 14.1p.

For the name field, it works as expected, as shown above.

However, for the referenceId field it is no longer honoring the validOperators.



Thanks

[stonebranch2]

Hi Isomorphic,
Do you have a follow-up for us on this?
Thanks

[Isomorphic]

Yes - a change was made in 2023 that limited the operators available to foreignKey fields - we're looking into it today will update here shortly when a fix has been applied.

[stonebranch2]

Thank you

[Isomorphic]

We've made a fix to prevent your custom validOperators from being clobbered with the default set for FK-fields in the FilterBuilder.

Please retest with today's build, dated March 23, or a later one.

[stonebranch2]

Thank you,

We haven't seen any builds for 14.1p since the 19th.

Can you please provide an ETA for availability.

Regards

[Isomorphic]

We're looking into this issue with the nightlies - we'll update here when we have more info.

[stonebranch2]

OK. Please do keep us posted, as this is urgent for us.
Thank you

[stonebranch2]

Hi Isomorphic,

Sorry to be persistent here, we don't normally push like this, however, we have a major release coming March 31, and applying this fix so we can do testing around it is urgent for us.

Also, do you have any kind of public changelog for changes between build Version v14.1p_2025-03-03 and the upcoming build?

Thank you for your understanding

[stonebranch2]

Hi Isomorphic,

There are still no daily builds available for 14.1p.

Can you please provide an update?

Thank you

[Isomorphic]

We do have somebody looking into the 14.1 build failures but no solution has yet been reached. We'll update when we've got things fixed.

[Isomorphic]

Apologies for the delay on this - there are 14.1 builds available now at smartclient.com/builds.

[stonebranch2]

Thank you!

[stonebranch2]

Thank you,

So far so good with verification.

Do you have a changelog for what changed between Version v14.1p_2025-03-03 and Version v14.1p_2025-03-26, even if very high level?

This would be helpful for us.