No it’s not. What does DevTools say while running the dashboard?
Can I ask a question?
You created BAQ DataViews.
But you’re using “Provider Model”. This will NOT populate your dataview automatically.
EDIT (Sorry, hit post before I intended).:
Note that even though I have a “BAQParentView”… it is empty. Instead, I didn’t tell Epicor where to store it, so it created its own temp dataview and stored the results from the BAQ call:
You need to EITHER, use an event to call your BAQ and steer the results TO your dataview… OR (much easier if you’re using provider model)… you HAVE to set this property on your parent’s Grid Model > Provider Model:
If I set that value:
The data lands in the correct dataview:
And my child grid can then use the pub/sub bindings you set up and get results.
I believe you are mistaken.
Sorry, I hit respond before I finished my thought… see above.
Cool.
Yes, if you don’t use the wizard, you’ll have to remember to set it yourself.
I noticed a problem in the 2025.2.14 release notes PRB0272725 where if the parent value starts with a 0 it does not work… IDK…
Yeah, I’m not saying I’m correct in this particular instance… but I can recreate the pub/sub not working if that one setting is not entered.
If you’re not using “events” to populate your dataviews, the Provider Model will do it for you… IF you set that property and tell the data what dataview to land in.
If not it lands in a temp dataview. For example, I didn’t define that property for my Child grid… and the results got pushed here:
@Randy, I’m not entirely sure what you’d like me to show. Could you be more specific on what data you’d like to see?
…I can’t even!!! Oh my! WOW! That was the issue. Thank you all for your help!!!
We’ve all be there. One silly typo and it takes hours to find it! 
Well, hopefully this post will help someone else in some way…even if it’s just for a good laugh. lol
Can you do me a favor… can you mark the below post as the solution?
Post (4) I believe. @Randy provided the solution. The other 30+ posts were just troubleshooting a mistype.
I used to use the Where List in Provider Model but then I discovered the Parent Child relationships and this is a much better/simpler way IMO. See my notes below.
I have seen the Parent Child Relationships behave strangely, e.g. not showing columns when they are actually there, but it should work if you start with a clean slate.
Linking Grids Using Parent Child Relationships
- Create your dashboard with the first (parent) grid and dataview.
- Add a new dataview for the second BAQ.
- Edit this dataview and set up a new Parent Child Relationship with the parent set to the first dataview. Set the parent and child columns that connect the two grids.
- Add a new panel card grid. Position this grid below the parent grid. Run the grid guided setup and connect it to the new dataview you just created. In Data > Grid Model > Provider Model, enter the Baq ID and check the Set Default checkbox.
- Add an OnRowChanged event for the parent dataview to expand the second grid. Add a property-set widget to the event and set it to change the Expanded property of the second grid to true.
- Save and preview the application.
When you select a row in the parent grid, the parent column you specified determines the rows displayed in the second grid.
Ya, I’m not understanding why I still can’t get it to function that way, but at this point…if I can get it to function at all I am super happy! 
And just in case someone runs across this thread in desperation.
The parent grid has to have the columns exposed to the child dataview. Regardless if you have set the parent child relationship up in the child dataview, if the columns don’t exist in the parent (hidden or not), which can happen if you misguidedly thought that unchecking visible in the Grid Guided setup, meant setting the Hidden property.
An easy way to confirm that all the parent columns in the parent child relationship exist is debug at runtime and take a look at the list of columns of the currentParentDataRow of the Child dataview.
Here is an example:
The fix manually add the column in my instance I was missing company. I added it manually and made it hidden. It then appeared in the currentParentDataRow list.
Moral of the story when using the Grid Guided Setup Wizard… Don’t uncheck the visible columns. Go back later to hide where appropriate. I was under the assumption if you just untick visible then it would add the column as Hidden which is not the case.
The thing to point out is that while the debugger mentions currentParetDataRow, it is referring to the currentParentGridRow, not the Row of the Parent Dataview. Confused? I am…
And yes this guy was me up until a the penny dropped
I am sure all of this stuff is not good for anyone’s mental health. IDK…