Importing TPI Data To ITrack - Revision history

Codeman: Update with more recent info

2018-06-08T16:19:41Z

Update with more recent info

@@ Line 16: / Line 16: @@
 If you're familiar with SQLYOG this would be the quickest way to work with the data. However the character limits on some fields in the TPI data aren't small enough for them to be imported by SQLYOG as external data. This is probably due to how much information customers put in to certain fields. So if you can manage to get the data imported into SQLYOG so can massage it, great. Chances are you won't be able to though, and should edit the data in Excel or something, then import it using Data Management.
 == What are the differences between ITrack and TPI data? ==
@@ Line 39: / Line 70: @@
 *Part ID is TPI's primary key, I believe. This can probably be ignored as a data point.
 *Condition = Category AND/OR Condition.
 == After Import ==

Nenjin: /* Massaging the Data File */

2015-12-04T17:04:41Z

Massaging the Data File

← Older revision		Revision as of 12:04, 4 December 2015
Line 34:		Line 34:
	*Internal Price is a TPI calculated price field. Ask the customer what they want that price to represent in ITrack, if anything.		*Internal Price is a TPI calculated price field. Ask the customer what they want that price to represent in ITrack, if anything.
	*Truck Make/Model = Make/Model in ITrack.		*Truck Make/Model = Make/Model in ITrack.
	*Part Make = pmanufacturer. The export file does not seem to contain a "Part Model" field, so you either pull it from Truck Model, leave it blank or ask the customer what they want to see.		*Part Make = pmanufacturer. The export file does not seem to contain a "Part Model" field, so you either pull it from Truck Model, leave it blank or ask the customer what they want to see. Alternatively use the model stated for the inventory item in question. (If there's an Engine Model value for example, use that.)
	*Strip out any "Other" values for Makes/Models. We don't specify anything when there is no explicit make/model available in ITrack, so that's just useless text.		*Strip out any "Other" values for Makes/Models. We don't specify anything when there is no explicit make/model available in ITrack, so that's just useless text.
	*Stock Number = Tagnum. However ask the customer if this is the # they want to use for Tag#.		*Stock Number = Tagnum. However ask the customer if this is the # they want to use for Tag#.

Nenjin: /* Massaging the Data File */

2015-12-04T17:03:30Z

Massaging the Data File

← Older revision		Revision as of 12:03, 4 December 2015
Line 29:		Line 29:
	== Massaging the Data File ==		== Massaging the Data File ==
	*It's probably best to divide the data file into separate files for each part type. That way you can isolate the "More" field data. If you DON'T do this, and just try to import the entire file at once, you will be unable to correctly map each part type's "More" field data, among other things. There are so many part type specific fields jammed into the inventory records, if you want to preserve all the customer data you're going to have to break it apart this way.		*It's probably best to divide the data file into separate files for each part type. That way you can isolate the "More" field data. If you DON'T do this, and just try to import the entire file at once, you will be unable to correctly map each part type's "More" field data, among other things. There are so many part type specific fields jammed into the inventory records, if you want to preserve all the customer data you're going to have to break it apart this way.
	*Category Name ~~gets converted~~ into Typenum ~~based on the Part Type name~~. You can ignore Category ID, those numbers will not agree with ITrack Typenums.		*Convert Category Name into Typenum. You can ignore Category ID, those numbers will not agree with ITrack Typenums.
	*Price = Sugggestedprice.		*Price = Sugggestedprice.
	*Wholesale Price = Bottomprice.		*Wholesale Price = Bottomprice.

Nenjin: /* What are the differences between ITrack and TPI data? */

2015-12-04T00:00:28Z

What are the differences between ITrack and TPI data?

← Older revision		Revision as of 19:00, 3 December 2015
Line 22:		Line 22:

	* TPI calls Part Type "Category" in their system.		* TPI calls Part Type "Category" in their system.
	* The "More" fields from ITrack are broken out by part type in TPI data. So EVERY inventory record contains fields for Engine Dimensions, Differential Ratios, Suspension Lengths, Wheel Diameters, etc...So for any given inventory line, there are a lot of ~~uselessly~~, empty fields.		* The "More" fields from ITrack are broken out by part type in TPI data. So EVERY inventory record contains fields for Engine Dimensions, Differential Ratios, Suspension Lengths, Wheel Diameters, etc...So for any given inventory line, there are a lot of useless, empty fields.
	*The Make/Model/Manufacturer information is handled the same way. Every inventory line has fields for Engine Make, Engine Model, Transmission Make, Transmission Model...regardless of what part type you're dealing with.		*The Make/Model/Manufacturer information is handled the same way. Every inventory line has fields for Engine Make, Engine Model, Transmission Make, Transmission Model...regardless of what part type you're dealing with.
	*What this means for the import is: the data is spread out across the whole inventory file in different fields. Which makes importing it all cleanly in one go through the Data Management screen difficult.		*What this means for the import is: the data is spread out across the whole inventory file in different fields. Which makes importing it all cleanly in one go through the Data Management screen difficult.
	*TPI make/model/manufacturer names rarely match Pro's exactly.		*TPI make/model/manufacturer names rarely match Pro's exactly.

	== Massaging the Data File ==		== Massaging the Data File ==

Nenjin: /* After Import */

2015-12-03T23:37:37Z

After Import

← Older revision		Revision as of 18:37, 3 December 2015
Line 42:		Line 42:
	== After Import ==		== After Import ==
	*If you inserted the data "as is", you'll want to run something like:		*If you inserted the data "as is", you'll want to run something like:
	<source lang = 'MySQL'>~~update~~ `inventory` ~~set~~ `pmanufacturer` = "CAT" ~~where~~ `pmanufacturer` = "Caterpillar";</source>		<source lang = 'MySQL'>UPDATE `inventory` SET `pmanufacturer` = "CAT" WHERE `pmanufacturer` = "Caterpillar";</source>
	once the import has happened.		once the import has happened.

	*You'll want do this for the major manufacturers, at least. The user is capable of doing it themselves but involves manually updating all inventory records by hand, which can be a pain for them.		*You'll want do this for the major manufacturers and models, at least. The user is capable of doing it themselves but involves manually updating all inventory records by hand, which can be a pain for them.

Nenjin at 23:36, 3 December 2015

2015-12-03T23:36:59Z

← Older revision		Revision as of 18:36, 3 December 2015
Line 42:		Line 42:
	== After Import ==		== After Import ==
	*If you inserted the data "as is", you'll want to run something like:		*If you inserted the data "as is", you'll want to run something like:
	update `inventory` set `pmanufacturer` = "CAT" where `pmanufacturer` = "Caterpillar";		<source lang = 'MySQL'>update `inventory` set `pmanufacturer` = "CAT" where `pmanufacturer` = "Caterpillar";</source>
	once the import has happened.		once the import has happened.

	*You'll want do this for the major manufacturers, at least. The user is capable of doing it themselves but involves manually updating all inventory records by hand, which can be a pain.		*You'll want do this for the major manufacturers, at least. The user is capable of doing it themselves but involves manually updating all inventory records by hand, which can be a pain for them.

Nenjin at 23:34, 3 December 2015

2015-12-03T23:34:29Z

← Older revision		Revision as of 18:34, 3 December 2015
Line 43:		Line 43:
	*If you inserted the data "as is", you'll want to run something like:		*If you inserted the data "as is", you'll want to run something like:
	update `inventory` set `pmanufacturer` = "CAT" where `pmanufacturer` = "Caterpillar";		update `inventory` set `pmanufacturer` = "CAT" where `pmanufacturer` = "Caterpillar";
	You'll want do this for the major manufacturers, at least. The user is capable of doing it themselves but involves manually updating all inventory records by hand, which can be a pain.		once the import has happened.

			*You'll want do this for the major manufacturers, at least. The user is capable of doing it themselves but involves manually updating all inventory records by hand, which can be a pain.

Nenjin: /* Massaging the Data File */

2015-12-03T23:33:17Z

Massaging the Data File

← Older revision		Revision as of 18:33, 3 December 2015
Line 35:		Line 35:
	*Truck Make/Model = Make/Model in ITrack.		*Truck Make/Model = Make/Model in ITrack.
	*Part Make = pmanufacturer. The export file does not seem to contain a "Part Model" field, so you either pull it from Truck Model, leave it blank or ask the customer what they want to see.		*Part Make = pmanufacturer. The export file does not seem to contain a "Part Model" field, so you either pull it from Truck Model, leave it blank or ask the customer what they want to see.
	*Strip out any "Other" values for Makes/Models. We don't ~~use~~ that ~~and it~~'s just ~~a worthless field IMO~~.		*Strip out any "Other" values for Makes/Models. We don't specify anything when there is no explicit make/model available in ITrack, so that's just useless text.
	*Stock Number = Tagnum. However ask the customer if this is the # they want to use for Tag#.		*Stock Number = Tagnum. However ask the customer if this is the # they want to use for Tag#.
	*Part ID is TPI's primary key, I believe. This can probably be ignored as a data point.		*Part ID is TPI's primary key, I believe. This can probably be ignored as a data point.

Nenjin at 23:32, 3 December 2015

2015-12-03T23:32:06Z

← Older revision		Revision as of 18:32, 3 December 2015
Line 1:		Line 1:
			Note: This import process only refers to importing TPI into ITrack Pro.

	== What is TPI? ==		== What is TPI? ==

Nenjin: /* Massaging the Data File */

2015-12-03T23:31:12Z

Massaging the Data File

← Older revision		Revision as of 18:31, 3 December 2015
Line 26:		Line 26:

	== Massaging the Data File ==		== Massaging the Data File ==
	*It's probably best to divide the data file into separate files for each part type. That way you can isolate the "More" field data. If you DON'T do this, and just try to import the entire file at once, you will be unable to correctly map each part type's "More" field data ~~correctly~~, among other ~~tihngs~~. There are so many part type specific fields jammed into the inventory records, if you want to preserve customer data you're going to have to break it ~~out~~ this way.		*It's probably best to divide the data file into separate files for each part type. That way you can isolate the "More" field data. If you DON'T do this, and just try to import the entire file at once, you will be unable to correctly map each part type's "More" field data, among other things. There are so many part type specific fields jammed into the inventory records, if you want to preserve all the customer data you're going to have to break it apart this way.
	*Category Name gets converted into Typenum based on the Part Type name. You can ignore Category ID, those numbers will not agree with ITrack Typenums.		*Category Name gets converted into Typenum based on the Part Type name. You can ignore Category ID, those numbers will not agree with ITrack Typenums.
	*Price = Sugggestedprice.		*Price = Sugggestedprice.
Line 37:		Line 37:
	*Part ID is TPI's primary key, I believe. This can probably be ignored as a data point.		*Part ID is TPI's primary key, I believe. This can probably be ignored as a data point.
	*Condition = Category AND/OR Condition.		*Condition = Category AND/OR Condition.


	== After Import ==		== After Import ==