Hi Folks
I ran into a little problem that I have mostly solved.
I’ve made a layer on top of the UD01 application.
It has a grid powered by a dataview which loads from a BAQ which has one parameter part number.
The user can select their data then click a button to call a function that prints a label.
It’s been working for months.
The users have changed their requirement and want the parameter to be job#.
As the BAQ is used in a few places I made a new one with the JobNum parameter - it works.
First problem: When you change the BAQ in the dataview it no longer loads on screen. Even if you use guided setup. Solution - I found the old BAQID was also in the Provider Model properties of the grid - changing the BAQID to the new ID solved it.
Second problem: I needed one new field from the BAQ to show up on screen. You guessed it, job number. It does not show up in guided setup.
Solutions - there are a few. The easiest one I found was to close the application, reopen it and it is now in guided setup.
Last issue: When you run the application it requests a job number parameter - good. But then it requests the old part number parameter which no longer exists on the the BAQ.
I looked through the grid properties and could not find anything. Any ideas?
Or is it a event that was automatically generated when I added the original BAQ?
A bit of an update but my findings did not help but it did narrow it down.
I noticed that there was a [DataView]_Get event created when the grid was created.
And it had an erp-baq widget , in it it had BAQ parameters to the original old BAQ
I removed that. It did not fix the problem
I removed the widget, it did not fix the problem.
So I am thinking somewhere else there is another reference to the old BAQ. I have not found one in the Grid properties (aside from the Provider Model->BAQID which I fixed last post)
Now when I load the page it asks for the Job parameter (correct) then the part Paramater (not correct) but when I refresh the grid it only asks for the job. So it is not a grid even apparently.
Solved
There was an unused data area with the same parameter. And it was on a hidden grid.
Fun fact - It was not caught initially as apparently if 2 paramaters are the same (PartNum for both grids) it asks for it one time.
It only came to play when I changed the BAQ.
Unhiding and deleting the second grid did the trick.
This was from way back a hidden ticking time bomb. It didn’t ‘hurt’ anything but would have made daily operations frustrating. No it did not go to live. We caught this in Pilot when the BAQ was changed. Developer tools did not show the events firing so it was a methodical search, event by event and control by control that found it after reading the raw JSON from the published export.
