Opportunities by Family(Top 10)

Owned by Georgios Vasilakos (Unlicensed)
Mar 20, 2023
2 min read

General description 

The purpose of this chart is to display the Top 10 number of Opportunities by each Vehicle Family, using a Kendo UI bar chart.

By using this chart the user can see the top ten opportunities and the model families that are related to.

The user can click on a specific family in the chart in order to access the opportunities grid list.

Layout 

Filters

The opportunities in this widget are filtered with the following logic:

  • If the logged in user is a manager then he will be able to see his own data and the data of the employees that he manages. In system terms this means that the manager can see the leads and the opportunities created or assigned to the team that he/she is defined. as a leader.

  • If the logged in user is not a manager then he will be able to see only his own data.

  • The logged in user can only see the Makes that he is allowed (by the dimension permissions).

  • Following the entity dimension depth (“Company”, “Branch” and “Location”), that is configured during the setup of the installation, the logged in user can only see data for the permitted dimension entity depth. For example, if the entity dimension depth is equal to Branch the logged in user can only see the data for the specific Branches of the Company and all the Locations of the permitted Branches.

  • Only Open Opportunities
  • Opportunities created in the current year.




Differences between widget & Opportunities grid list with the same filter

  1. The widget uses the following filter
    (Make eq 'LAND ROVER' and OPPStatus/Equals('O'))
  1. While the GridList filter uses:
    (U_IDMS_DIM_Make eq '65') and (OPPStatus/Equals('O'))

Both are using the IDMS_LEADSINFOVIEW entity, which calculates the Make attribute as follows:

case when 
    ifnull(mkoriginal."Name",'') <> '' 
then 
    mkoriginal."Name"
when
    ifnull(PLACEHOLDERVEHICLE."U_MnfctrName",'') <> '' 
then
    PLACEHOLDERVEHICLE."U_MnfctrName" 
else
    "Makes"."Name" 
end as "Make"

Here are the JOINs for that view:

left join "@XIS_MDLS" as MODEL on MODEL."Code" = "VOI"."U_IDMS_ModelCode" 
left join "@XIS_FMLYCR" as FAMILY on MODEL."U_CrFm" = FAMILY."Code" 
left join "OSLP" as "SPsPrevious" on "U_IDMS_SP2Code" = "SPsPrevious"."SlpCode" 
left join "@XIS_MFCTCD" as "Makes" on "Makes"."Code" = "Leads"."U_IDMS_DIM_Make" 
left join "@XIS_MFCTCD" as mkoriginal on mkoriginal."Code" = MODEL."U_Mnfctr" 
left join "@XIS_CARS" as PLACEHOLDERVEHICLE on PLACEHOLDERVEHICLE."Code" = "VOI"."U_IDMS_ItemCode"

So the Make value gets calculated as follows:

  1. If the VOI's model is not null, use the model's manufacturer name
  2. Else if the VOI's vehicle in not null, use the vehicle's manufacturer name
  3. Else use the Lead dimension Make's name

For that reason the U_IDMS_DIM_Make is not always reflected in Make. Also the U_IDMS_DIM_Make is a dimension attribute, and should not be included in neither the View's nor the Filter's logic.