uStore Dependent Dropdowns values major bug found 17.1 - escalated to R&D

[markb]

Hi all,

We've upgrade to latest versions of everything recently and the upgrade has gone fine except for one major client facing issue with 100s of products on uStore in our environment.

The issue is related to dials with dependent drop downs and what seems to be happening, is the uStore front end is not correctly gathering or selecting values to transport to the backend for uProduce to generate jobs with the complete or accurate information.

I've uploaded the dial configuration for the below videos.

As you can see in the below videos, I've unhidden the dials filtering to the dropdown dial and on-screen in the legacy multi-page product flow, the front end is selecting the values correctly from the SQL uStore data connection. 

If you click preview it can be hit or miss on the uProduce preview job to accurately transport the dial values to uProduce job.

If you click next and then back, you will have a higher chance of getting all dial values to populate to uProduce.

For the single page flow, no dial values are being selected at all based on the dial configuration of selecting the default field checkbox in the dial.

Legacy Multi-Page
https://youtu.be/Bfkqsx9sshM

Single Page:
https://youtu.be/D_vyDhzwRLc

To my understanding this may be related to this bug reported from 2023 and I do not believe this bug was re-solved:
https://groups.google.com/g/xmpie-users/c/pyhjt9RNm0c/m/qyHqx89nAQAJ

This is a serious client facing issue for us, we have 100s of products configured this way and this has been very surprising for everyone.

I am looking for any solutions to resolve this issue with existing products that anyone may have that could be communicated to R&D as a work around they could potentially apply to our enviroment.

We have spent days covering anything simple to resolve, but it seems to be something with the application or perhaps something unique to our environment.

If anyone can validate the bug on their end, please let me know.

[Wayne]

Hi Mark,

I am trying to understand the benefit of using depended dropdowns in your use case, rather than just doing this in Plan.

Sure it has been working but this workflow does seem inefficient to me.

Anyway - Check the browser dev tools to ensure no errors are being reported.

Also check the network communications to confirm what values are being retrieved or posted back - is the issue client side or server side.

Regards,

Wayne

[markb]

Hi Wayne,

I agree managing this in the Plan going forward. The dependent dropdown feature has been useful for us over the years. The only advantage at this point, is having multiple ways to do the same thing if one way stops working.

[couch]

It's a feature of the product, so if it is not working as documented, it should be reported to XMPie Support and handled as a bug with an expectation that a patch will be provided.

[markb]

Hi Couch,

Yes, support and R&D are aware since Saturday and I've posted here for good measure as I believe support and myself have checked what we can and R&D may not have had a chance to review, I am not sure.

[Eric Paul]

Mine was the post linked above - the bug has not been addressed nor have I received any updates from support (they closed my case when they sent it to R & D). And I can most certainly replicate the issue - which I have done with members of the support team, over weeks of testing to verify that there wasn't something wrong in my configuration in uStore or in my database.

[markb]

Thank you Eric, support has also spent hours investigating on our case and what we have confirmed outside of support is the incorrect proofs in uStore transport this information to both the uStore.OrderProductDialValue and  xmpdb2.TBL_Job.jobparams tables so the db post  does not look to working when you change the drop down menu.

Not only can dial information be missing in transport to the two db tables from uStore, but there can be "memory" of past dropdown selections from the front end and your proof can have mixed up data from different records you selected in the past.

[couch]

I'm told by the product manager that there has been a patch for the dependent dropdown list problem has been created and should be published in the next day or two.

[markb]

That is great news to hear for everyone who uses this feature!

[Wayne]

FYI - Single Page Dependent Dropdowns has an issue with default values - legacy works NG does not.

I have escalated to XMPie