Should we mantain Company = Company links in BAQs? What do you do?

Epicor ERP 10
1

Epicor defaults these links when tables are brought into BAQs. In the past, we were advised by an Epicor trainer that these links should be maintained even though we only have one company.

There is a performance hit on these queries and sometimes that hit is extreme.
The easiest remedy is to remove company from the join and add it as a table criteria constant: Company = UEINC.

But is it really needed for a single company operation? What is the risk of leaving it out (besides the overhead of reworking everything should we add another company).

2

Originally (back in V8) I ignored making those company=company relationships. Out of pure laziness.

If you ever add another company, you may have to go back and redo ALL your BAQ’s to make sure you don’t get data from both.

I think the extra couple of clicks to add it now is way better than having to fix a bunch of stuff later.

3 Likes
3

Even in a single company, you’re using the first part of the index for SQL server - so you can test it out to see the performance hit.

But I’m with Calvin, it’s just a good practice that future proofs your development.

1 Like