nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

2020 JMP AL Customer Add-in

tina_cui

The Annual Customer Add-in (AL Customer) is designed to collect and query customer information, account information and actual sales numbers for current and previous years from the SAS GIDB database. It can be used to analyze all current JMP annual license customers. The interface allows for selecting one or multiple territories, and one or multiple product groups. The background program of the add-in runs every night, therefore the add-in will query the most recent sales data.

The 2020 AL Customer Add-in made a few changes:

Update to 2020 sales territory
Add JMP Live to product group
Remove SASJMP bundles from product group
Data query 2019-2020 only

Current Version 2 made a few updates:

Add EUR, NA Beacon Accounts to the territory picklist
Add customer JMP release version
Add SAS Rep address

For support and question, please direct to tina.cui@jmp.com

2020 JMP AL Customers(2019-2020) add-in v2.0.jmpaddin

Comments

Tim_Pierce_JMP

Thanks Tina! Worth noting for those looking to use it right away that the territory assignment changes are not fully updated in the GIDB, so the data from the Add-in is not 100% yet. You can do some data joining/matching with the preliminary account assignments as a stop gap until that is complete.

tina_cui

@Tim_Pierce_JMP I can provide a historical data report if you need it.

rene_kleinhans

will the add-in work with JMP Pro 14.1? this is what I have on my desktop thanks

martindemel

The beacon territory is missing. As they now do not have an overlay role anymore, it would be good to have them in as well, also to not have their accounts in our lists

tina_cui

@rene_kleinhans It should work on both JMP14 and JMP15. Let me know if you find a problem.

tina_cui

@martindemel OK, I will update to have the beacon territory.

MikeD_Anderson

Could we get the address fields from the GIDB records as well? I use them for geolocating the locations of my accounts.

ChristianStopp

If I might piggy-back, perhaps the JMP version they (theoretically) have as well? Thank you!

MikeD_Anderson

piggy-backing on @ChristianStopp 's piggy-back... Since there are only a few more fields, could we maybe get either the ability to choose the fields we want or get all of them by default?

tina_cui

@MikeD_Anderson, if only a few more fields, I will add to the next version by default. If a bunch of fields wants to be added, I may re-program the add-in to have the ability to choose the fields.

MikeD_Anderson

@tina_cui - Looks like there are about 70 total fields according to what Atlas can pull using it's GIDB query. You've got 36 in there already.

tina_cui

@MikeD_Anderson the add-in designed to have a quick report for the sales team, it's unnecessary to pull all the fields. I could re-program to choose the fields in the next version.

MikeD_Anderson

@tina_cui - Thanks for the update! The update will make my workflow a lot faster. One more thought - and I'd put this under "important, but not urgent." Having a time stamp for when the data was pulled can be useful. Maybe as a table variable and/or included in the final table name. With something like GIDB that updates as new accounts are added, knowing the vintage of a data set can become important for those using it.

Thanks again!

Best,

tina_cui

@MikeD_Anderson that's a good idea, I will check if GIDB has a timestamp column.

MikeD_Anderson

@tina_cui I was thinking something like this:

Names Default To Here( 1 );
dt = Open( "$SAMPLE_DATA/Big Class.jmp" );
dt << New Table Variable( "Query Date", Char(As Date(Today())) );

Except dt is pointing at the final report table.

tina_cui

@MikeD_Anderson thanks. The add-in read-in from a SAS table, the table update daily. I am thinking if GIDB has a timestamp field, that would be accuracy, otherwise, I could do like you suggested or program into the SAS table.

Tim_Pierce_JMP

Hi tina_cui, If I may request another feature request for the next version of this Add-in:

There are two additional fields in the GIDB that would be useful to AE's to help identify non-standard accounts.

1. The field "Key Account", which populates with initials or no data.

2. The field "Multinational Account?", which populates with either Y or N.

This was discussed in our recent East team meeting and agreed that this could be used broadly.

Let me know if you need more clarification on the fields or why they would be useful.

Tim

tina_dubois

@tina_cui when you update the version for 2021, can you please add a column for Ref4 number or Contract number? That is helpful to have as well.

Tim_Pierce_JMP

Hi @tina_cui ,

Hope you are doing well! I encountered an error this week when trying to use the 2020 JMP AL Customers Add-in and confirmed with someone else they get the same thing. It throws the following error:

If there is an easy solution before we all move to the 2021 version, please let me know.

Thanks,

Tim

isabelleswaenep

Hi, @tina_cui

We've been working on France Territory but the Add In made an extract only on France T1, and not France T2.

Could you please make an update with both territory?

Many thanks.

Isabelle

andyzhou

Hi, @isabelleswaenep

I'll be taking over this add-in starting this year, and I can definitely make sure that the full France territory (containing both France T1 and T2) is included.

Management is currently still reviewing final territory definitions, so it'll take some time before the data behind the add-in is accurate and up-to-date with 2021 territory definitions. Once that's set, a new version of the add-in for this year will be available (hopefully will be done later this month or early February).

Best,

Andy

JerryFish

Ditto @Tim_Pierce_JMP 's comment above on "Connection Failed." Can't get to the 2020AL's or 2019's for that matter. Anyone have a fix?

Thanks,

Jerry

andyzhou

@JerryFish @Tim_Pierce_JMP

I'm working on a new version of this add-in that will pull in invoice level data, and that problem should be resolved in this new version. I should have it ready for use in the next few days!

Best,

Andy

JerryFish

Thanks @andyzhou ! I'm sure you're already feeling pressure from other teams and working as hard as you can. It will certainly be heavily used as soon as it is up & running!

Jerry

Tim_Pierce_JMP

@andyzhou, Thanks so much for working on this Add-in. It is really useful for our territory plans and prioritizing our accounts when territory changes happen like this year!

andyzhou

Please see 2021 JMP AL Customer Data - Add-in to Come! for an update!