When I have only the Part table in a BAQ, and the display field is PartNum i get this error and i cannot save or analyze.
When i have only the Part table in a BAQ, and i make a calculated field for PartNum, not even casting it as a VARCHAR, just put the same field in a calculated field as is, i do not get this errror
I’ve had a support ticket open for weeks on this but no response, so i’m coming to you guys.
Additional context, old BAQs where Part.PartNum already exists in the BAQ work fine, no errors. If i add Part.PartNum to an existing BAQ, or create a new one as above, i get the error.
Try adding the field Part.Company to your BAQ. I think those two fields would normally constitute the primary key, as the DMT template builder shows them as mandatory.
If running multicompany…maybe you don’t have permissions to all companies?
I am a security user, have all permissions etc. Also not my first time doing this type of thing so it’s very odd that this has come up.
We are multi-company, I’ve also tried adding criteria for each one, they all return this error.
SQL works fine, which is where I do most of my work, so i’m unsure exactly when this might have started. Had to build a BAQ in Epicor which is when i found this error. Again, old BAQs work just fine so this is very very strange.
I actually did escalate my ticket earlier this morning so thanks for that, we’ll see where that goes. Any other troubleshooting methods i could do?
I’ve tried looking for PartNums that have strange characters, begin with spaces etc but nothing comes up, i used LEN(Part.PartNum) and went through all the ones that didn’t line up with our 6 digit standard. Nothing new has been created.
Sorry…wish I had better ideas. Seems odd that old BAQs work but you can’t construct new ones without that error.
Only other odds and ends I can think of - clear out the sort order in the BAQ if there is one, maybe run some health queries via SQL to check constraints etc.
Yikes…sorry it’s gone from bad to worse. Two master tables throwing the error seems to point to a larger problem. If you can get to the data in SQL without them popping up…that’s good…at least the data tables are hopefully intact. Good luck.
Are there any hints in the SQL produced in the BAQ phrase? That’s the part that starts like so:
/*
* Disclaimer!!!
* This is not a real query being executed, but a simplified version for general vision.
* Executing it with any other tool may produce a different result.
*/
Only hint may be the fact that going to the General TAB to look at the query phrase causes the error to repeatably come up, had to force close Epicor to be able to do anything.
The ‘Query Phrase’ is blank, that section you posted that normally shows up doesn’t even show up.
Well that ain’t good. One more thing to try - I’ve seen a few instances where the classic client and the browser client BAQ have functionally parted ways. What happens in the browser client BAQ?
Thanks for the suggestions, I have not tried recycling the app server, we did do a data model regen end of March as part of a different project, feel that’s recent enough that this problem existed prior to that already.
Tried opening Kinetic in browser but i couldn’t due to some Edge Agent not running, both of these are over my head and will pass this off to our IT Department to review.
That’s a misleading error, it’s not an edge agent problem. It means that menu hasn’t been configured to be browser-compatible. When that happens, the browser client attempts to launch a new desktop session via edge agent, which is nominally supposed to support printing.
This is a really important message if you’re SaaS. The desktop client is going away at version 2026.1 so the edge agent failover method is going to stop working soon.
Naming a calculated field with the same name as an included table in the query could be the issue.
Try a calculated field of PartNumber or PartNo, for CustID use CustIdent.
Related, but not shown is when you try a calculated field and set the data type to the wrong type. In your two cases, this wasn’t the case. I have made this mistake with an AR Invoicenum - which as a VarChar not a Int which it should be.
