Importing the SKU

Portal User asked a question.

June 27, 2018 at 7:00 AM

Importing the SKU

In SLM8 I've been using the application name to do my matching to the SRS database during the import and I just realized the wizard's not been storing the manufacturer SKU I've been putting in the SKU column. Of course, if I switch the match to the SKU field it'll pull it in but I have some vendors where the skus are most likely not present.

I thought the sku was imported regardless, in SLM7 but could be wrong.

Has anyone asked Support about this already?

Thanks,

Mary

ScouseSAM
8 years ago
Hi Mary, With the import function this is an either/or situation. If you are importing based on Application Name then there is no SKU "destination" to map and therefore it won't import the SKU you enter because essentially, it doesn't read that cell in the import sheet. Likewise if you choose to import based on SKU , you're unable to map to an Application Name destination and it won't read that cell. I guess having both could cause a conflict, particularly if importing based on SKU. If you were to import based on SKU, I suppose you wouldn't really need to input the application name manually because there should be a direct, universal relation between the SKU and the application name. I don't know if you're able to change field mappings in the back end or anything? Might be worth a question to Snow if you feel it's something you would really benefit from.
Expand Post
- Portal User
  8 years ago
  Hi Craig, ‌ I figured that was the case; to avoid any confusion between the fields. I'm working with some known vendors, but too small for details like release date and skus to be proactively loaded by the SRS team, so I've had to use the application name to get my data in my system. I've experimented with adding the sku post import but that blows away settings on the record; specifically the incredibly valuable product description. I believe it also resets the metric and some of the check boxes at the bottom of the purchase tab. I figure changing the sku means your entitlement details may be different and Snow is trying to help you avoid any conflicting information but that's only making my situation worse. Adding the sku, then the product description, then verifying the remainder of the tab, for every license I just imported, is definitely not an option that's sustainable. An alternate solution would be to create a custom field for it. I found out the hard way, and got a confirmation on another post to the community, that the Application Part Number field is not displayed anywhere on the web interface. I was planning to use that for the reseller part number and instead have created a custom field. Cordially, Mary
  Expand Post

Related Product Forums

→ Flexera One

→ Snow Atlas

→ FlexNet Manager

→ Snow License Manager

→ App Broker

Need help finding an answer?

Ask a Question →

Importing the SKU