Oddly, yes, and why do you ask?
But I was right - not licensed:
OK… so you may have found a bug here…
- CRM (if licensed) triggers all sorts of extra security checks
- Territory is required
- based on your assigned salesperson ID, you may or may not be able to see customer data. This extra security is enforced with all queries.. even if you make a custom BAQ, the system adds on extra filters based on who you are
- If you DO NOT have CRM, then everything should show as normal. no extra checks or filters.
SO… @JasonMcD Please submit a support ticket. Let them know that
- you do NOT have CRM licensed
- The system is throwing messages that it should not show
- The system is filtering customers it should not filter
- Let them know which applications you are experiencing this in.
- Let them know that it did not do this in the smart client, and that this is a parity issue.
2 Likes
Appreciate it. We started with a ticket, and it is still open. I believe we have updated it with the findings (but not the CRM part yet). [EDIT: CRM notes are added to ticket.]
Not trying to be mean here, but I had to figure it out after the ticket was about to end with “Please send us your 300 GB database.”
Well, hope they do send it to dev. Not having a lot of success with that lately…
2 Likes
Do you guys have Epicor’s CRM module? It’s actually optional but they normally sell it in the standard bundle as if it’s required. I know Territory is required if the CRM module is enabled so that’s what comes to mind.
No, assuming I highlighted the right thing in the pic a couple posts earlier, we are not licensed for it.
1 Like
It’s the CRM module that makes it required and adds all the territory restrictions.
1 Like
Just to preserve some sanity, here it is working in Classic. Clearly showing blank territories but still showing customer ID.
Sigh Totally agree. But ~7 months from now, we will have no ammo in that weapon, right? Then all defects will be working as designed, with no client to measure against?
6 Likes