DataSource XML fields parsed as Field instead of DataSourceField on startup

[stonebranch4]

Hi,
This issues was fixed in version 14.1p-07-01-2026 build and I am trying to test again with the latest version of 07-18-2026 build and it looks...

[stonebranch4]

Thank you for the quick response.

[stonebranch4]

Hi,
Could you please provide an update on this? I appreciate your help.

Thanks

[stonebranch4]

Hi,
These are the smartgwt provided ds.xml files shipped from smartgwtpro.jar file.
further debugging I noticed the following ds.xml files...

[stonebranch4]

Hi,
We have recently upgraded the client libraries to 14.1p-2026-06-19 and we are noticing the following warning messages on startup.
...

[stonebranch4]

I am able to test using the link provided and it looks good now.
Appreciate your quick response and support.

We can close this now....

[stonebranch4]

Thank you for the quick response. Sorry I thought it will be fixed in show case too. I will test in my local and update you.

Thanks

[stonebranch4]

Hi,
If I add the <template> or <abc>, as specified in post#1, it still behaving the same. So the fix is to show the html elements ?...

[stonebranch4]

Thank you for the quick response. Is it fixed in today's build?
The show case is still showing the same.

Thanks

[stonebranch4]

Hi,
We recently noticed that, certain values in the combobox item is blowing up. The closest I can reproduce is here in the show case.
ht...

[stonebranch4]

Hi,
Yes you were right I reported in reverse order for skin issue and we are good with it now.
we have also fixed our code based on your input...

[stonebranch4]

Hi,
We have noticed that Class for RadioGroupItem is changed for locators.

They are now showing up as "...||Class=RadioItem]/element",...

[stonebranch4]

Hi,

Sorry there was a confusion and we sent the wrong details. can you please check the post#11.

Thanks

[stonebranch4]

Hi,
Can we please have an update on the skin issue?

Thanks

[stonebranch4]

Thank you for the clarification about the locators & skins.

Related to the calendar issue, we noticed that it used to fire addDateChangedHandler...