Territory field not getting filtered for Cases/opportunities!!!!!

By | May 30, 2009

Are you facing the problem with the territory field like it is not getting populated properly in Sage CRM?

If yes, then here is the one more area that you can look into.

The problem arises for entities like Cases and Opportunities. In Sage CRM, we can create the mirror imaged fields of Case/Opportunity in the CaseProgress/ OpportunityProgress table respectively.

For the standard entities like Case, opportunity the field case_secterr and oppo_secterr are already present by default, but this is not the case of CaseProgress and OpportunityProgress tables. Here you will not find these territory fields.

Now, if you will create the field, say Case_Secterr in CaseProgress table which maps to Case_Secterr of Case table, you will come across the problem mentioned above that is the territory field not getting populated properly.

Here, exactly what happens is, CRM does not use the actual territory field from Case table. It automatically, fetches the territory field from CaseProgress in the whole system. Due to this conflict, it does not filter the territory field on all the screens, where it has been added. It displays all the territories available in the CRM.

If you find this useful, Please drop us a mail on crm@greytrix.com.