Deployed Dashboard - behaviour change between 10.1 and 10.2

Hi

Another weird difference between 10.1.600 and 10.2.300. I have a deployed dashboard with a customisation applied on top - customisation is just to allow a user to input a time in xx:xx format, and then in code I convert this to seconds past midnight and put it into OrderRel_Number01 field. The dashboard is updateable, so Epimagic used to take care of putting this UD field back into the database.

Since upgrading, my custom code isn’t working. I have found that the Afterfield event on the “Results” table, now refers to the wrong BAQ. I think it was luck previously, but can’t see where to actually tell it which BAQ the “Results” table should reference…

E10.1.600

E10.2.300

There are 2 BAQs on this dashboard - the main updateable one, then a subscribed one at the bottom just pulling in a couple of fields from Customer table

If it isn’t possible to tell it which BAQ the “Results” table in Form Event Wizard should reference, should I instead update the underlying EpiDataView? (disclaimer: I have tried doing this, but it wasn’t taking the value and updating it when saving)

Fixed it - for anybody else seeing this thread what I had to do was to delete the main BAQ from the dashboard, then add it back in again, then redeployed UI.

It seems that the change between 10.1 and 10.2 is that on 10.1, the “Results” dataview on the UI was the first BAQ that got added to the dashboard. In 10.2, it seems to be the last BAQ added to the dashboard.

@Rich can you confirm whether this is intended behaviour? I will hunt you down at Insights to chat about it :laughing:

I am not aware of any changes in this area - checking.

Look me up at the Opening Reception or Wine and Cheese and I will buy you a free drink!!

I’ll have to pick something “off menu” to ensure that you carry through on that offer of “buying” me one… I like pints of Vodka. :rofl:

Actually, all the help you give on this forum I will be the one buying you a pint of spirits - thank you!