Yes.
1 Like
So interestingly… I can’t successfully unpack your original export. I imported it into my system and exported and that I could unpackage. Your copy above I get this trying to unpack
2 Likes
What version are you on? Its probably not backward compatible?
1 Like
I exported the same version as you no mismatch there.
I did find in your export the and/or for the relationship is empty but my export it came out with “and”
I suspect a UI bug is breaking that part and it’s self correcting on import/export
2 Likes
Yep, I suspect that too.
1 Like
It is self-correcting on running and it does not change any significant field on export/import at all.
Are there any errors in the browser console when it is not switching correctly?
1 Like
I don’t know, its already fixed now since I re-imported it.
1 Like
Can you restore a prior version of the DB to just before the re-import to another instance? Not sure how that process works in Cloud.
4 Likes
It’s probably the same bug I caught in a different context.
My copied subqueries table criteria were linked.
Reimport I believe did fix the issue.
3 Likes
I had that same issue. I had to click on the background canvas once or twice before clicking on the other table in order for the Table Criteria context to properly switch to the other table. The BAQ Designer seems to have several issues like this.
4 Likes
Yes, I’ve definitely adopted a “learned behavior” to workaround expected issues, especially when interacting with App Studio or BAQ/BPM Editors (The stuff that doesn’t use the typical Epicor MetaUI screens).
For example:
- Don’t click into “DataSet” when setting up a kinetic-rest component in App Studio, which unexplainably breaks your kinetic-rest component until it’s deleted and re-created. This issue has been there seemingly forever.
- Complex condition chains within an AppStudio Event tend to spontaneously ‘poof’ themselves, so I split up my events using event-next so there’s only one or two conditions in each event to avoid losing my work.
- I click into the “blank” area in BAQ/BPM/AppStudio in between selecting each object, because all of these designers tend to “hold on” to some properties of various objects if i don’t. I wonder how much this contributes to my carpal tunnel.
- BAQ Editor will only let you check 80 things at a time.
- BAQ Editor sometimes unchecks or checks things for you in display fields as you are scrolling down the list and checking things.
- Display fields from a different table sometimes show up in another table or subquery.
A majority of these issues are worked around by saving, then pressing f5 (reloading the browser page) - so there’s another learned behavior. save, f5. save, f5. save, f5. 
5 Likes
If you look closely at the video I made you can see the context is switching to the other table. This is different.
1 Like
Shot in the dark here, but did you save your BAQ after adding the tables but before adding the criterias? I can imagine the table GUID to be empty until the BAQ is saved, maybe?
1 Like
Yep. Saved, closed, reopened.
1 Like