We have a customized version of part entry that is behaving completely differently in App Studio compared to when we publish it and put it on menu maintenance.
Steps to Recreate:
Create a BAQ listing all parts in the system ( Table: part, Display fields: PartNum)
Create a new layer for part entry in Application Studio
Create a new dataview in App Studio (name it whatever you want)
Add a new panel card grid to the “Activity” page
Link the panel card grid to the newly created dataview (Data-> Grid Model → Ep Binding)
Place a button in the top section of the panel card grid
Create a new on-click event for the button (behavior-> on click)
Add a next event widget to the on click event
Call the “get” event that was created for the data view in the “next event” widget
Add a “property-set” widget to the on click event
Set the “expanded” property of the panel card grid to false
Add a “property-set” widget to the on-click event
Set the “expanded” property of the panel card grid to true
Save your work (These steps should get you a grid with a clickable button)
Click the preview option
Select a part
Go to the “Activity” tab and click the button (this should load the dataview and collapse / expand the panel card grid)
Click the publish button
Open the main copy of the menu for a part entry module to the current company
Apply the custom layer to the menu item
Close your browsers
Open a fresh browser
Launch the modified part entry screen
Select a part
Go to the activity tab
Click the button
The customization will work as intended, collapsing and expanding the panel card grid correctly in Application Studio. But when you do the same from a menu-launched item, you get something that looks like this:**
**
This can be remedied by clicking the little arrow to the left of the header twice (once to collapse the panel card, once to expand the panel card) after the event is done running.
Has anyone else run into this or know of a way to get around this? I added a wait function in between the collapse and expand events, but that doesn’t seem to help.
Not sure what unexpected behavior you’re experiencing but the first thing I’d try if a timing or race condition is suspected is to add another event-next after step 9 and put your property-set actions in another event.
It’s dumb the collapse/expand hack is the only way to affect grids for lack of proper event hooks.
I happened to face the same issue yesterday on Public Cloud 2026.100.9 in Pilot. In short, when the panel card grid was expanded with “property-set”, some error occurred saying the “model” property was undefined.
Manually expanding the panel card grid by clicking on the little arrow worked, so I thought why not I just simulate the click event using Javascript, and then it worked lol. You can try the workaround below and see if it works for you. Not sure if introducing delay with “dashboard-timer-set” and “dashboard-timer-clear” are still required but since it worked for me I just leave it as is.
I tried the workaround you mentioned and I get the same result. It works perfectly in application studio but fails to fully expand the grid when running from a menu item.
Do you think increasing the “Wait command” would help at all?
I tried what you suggested and still got the same results. It works as it should in application studio, but when launched from a menu item it still fails to expand the grid fully.
