If you have some particularly heavy queries that need to run often, or that you need to run at maximum performance, one really good way to deal with them is with SQL views or table-valued functions, and external BAQs… You still retain the usual Epicor BAQ facilities with some minor differences, but also get the full performance of native SQL code. This is also very useful if you need to use constructs Epicor doesn’t support natively, or makes more difficult to use, like APPLY statements or clever recursive CTE usage. The downside is that you have to manage deployment or migration of the SQL object itself manually, since it can’t be included in a solution. To make sure they survive Epicor’s own data structure utilities, make sure to create the views or functions in a schema of your own (not Erp or Ice).
You must manage security as well for company, plant, and territory. Any field security will not be enforced either so make sure you’re covering your GDPR/PII requirements.
This!!!
2 Likes