[Wayder]

Hi Brent,

Could you tell me what the Custom2 field in your SAS feeds is.


Thanks

Way...

[Mr. Sal]

Hi Brent,

Could you tell me what the Custom2 field in your SAS feeds is.


Thanks

Way...
Hi Wayder,

If I am thinking what you're thinking, I don't think Brent would be able to answer your question the way you're asking, because before I decided to reply to your post, I just went and check just two different CSN Stores datafeeds I am using, to make sure of this answer: It would depends on what of the different CSN Store datafeeds you need to know what is used on the Custom2 field.

Tip# 1

If you are asking because you want to use an old SAS script that may be calling Custom1 and Custom2, there is a way around that. :)

Tip# 2

So far I have noticed that I have no problen calling any of the CSN Stores datafeeds Real Categories and, (or) SubCategories, because so far... the CSN Stores are using the not so new by now (new SAS Dataffed Format).

So if you question is because you're using an old script that call Custom1 and Custom2 for that purpose, you can still use those same old pages script with just a modification to the import script.

If I made a mistake here, and that's not why you're asking about Custom2, then disregard this post. :)

[Wayder]

Hi Sal,

Thanks for your reply.

Now, I did initially think that you were thinking what I was thinking, but after reading your post I don’t now think that your thunk was what I thank :) Let me explain.

I had used the ProductID field (0) as a unique identifier and this has served me well with all of the SAS feeds (bar one) that I have used to date. I found however that this is an identifier create by SAS and that CSN has at times uploaded a new feed and have had the whole feed ProductID’s reallocated. http://forum.abestweb.com/showpost.php?p=816210&postcount=10 (about half way through his post)

This had the effect that all products in the CSN feed looked new to my script, therefore my script re-enters the new item (ProductID) and deletes the old leaving me with 20k+ 404’s. Not good :(

I put in place a 301 redirected using .htaccess but it took me a while and spiders read at least 8k of 404’s before I finally had it in place.

I have been thinking about this for a while and I thought that Custom2 looked suspiciously like a CSN SKU, so I thought that I would ask. If this is the case, I can use that column as my unique identifier.

Now I know Brent said “It isnt something that should happen again” but …. It happened before and if I can avoid that for the future, why not.

I didn’t ask an elaborate question, because sometimes a simple question can receive a surprisingly good answer even though it didn’t answer the question you originally asked.

[Mr. Sal]

If I made a mistake here, and that's not why you're asking about Custom2, then disregard this post.
So I was right! :yellowlau

I made a mistake again! (My last one anyway.) http://abestweb.com/smilies/cool_shades.gif

[Mr. Sal]

Hi Sal,

Thanks for your reply.

Now, I did initially think that you were thinking what I was thinking, but after reading your post I don’t now think that your thunk was what I thank :) Let me explain.

I had used the ProductID field (0) as a unique identifier and this has served me well with all of the SAS feeds (bar one) that I have used to date. I found however that this is an identifier create by SAS and that CSN has at times uploaded a new feed and have had the whole feed ProductID’s reallocated.

This had the effect that all products in the CSN feed looked new to my script, therefore my script re-enters the new item (ProductID) and deletes the old leaving me with 20k+ 404’s. Not good :(

I put in place a 301 redirected using .htaccess but it took me a while and spiders read at least 8k of 404’s before I finally had it in place.

I have been thinking about this for a while and I thought that Custom2 looked suspiciously like a CSN SKU, so I thought that I would ask. If this is the case, I can use that column as my unique identifier.

Now I know Brent said “It isnt something that should happen again” but …. It happened before and if I can avoid that for the future, why not.

I didn’t ask an elaborate question, because sometimes a simple question can receive a surprisingly good answer even though it didn’t answer the question you originally asked.
Like I said, you was right!

I didn't knew what you needed to know by the question you asked about the Custom2 field, we all have our own rant about the the Custom2 field. :yellowlau

Let me first explain why I reply to what I thought you was having a problem with:

By the time I joined the CSN Stores, I already had made a new SAS datafeed import script with the new datafeed format, so, so far I have not found any issue with any CSN Stores datafeed yet, but...

Since I still have some issues with other SAS merchants datafeeds about the way they still use of the old Custom1 and Custom2 field for the categories and subcategories, I thought that you may have encounter those issues too.

And while some of them may still have their categories and subcategories anywhere listed between Custom1 and Custom5, I found a way to deal with those merchants, as long as they're also using the new "merchantCategory" and the new "merchantSubcategory" fields.

But, since you're using the ProductID field (0) as a unique identifier, I can't say anything about that, because I use a different unique identifier for every record on my table.

So like I said before, just disregard my wrong answer, I was wrong again. :)

[Brent E.]

I have been thinking about this for a while and I thought that Custom2 looked suspiciously like a CSN SKU, so I thought that I would ask. If this is the case, I can use that column as my unique identifier.

Now I know Brent said “It isnt something that should happen again” but …. It happened before and if I can avoid that for the future, why not.


Happy Monday Wayder,

Custom 2 in the data feeds contains the SKU values that CSN uses. These values will NEVER change. They will be the same whether or not the issue that arose in the past(product ids being changed when we had the feed error) happens again. I am still waiting to hear from Brian whether or not the SAS product ID can be the same for each SKU. Right now when the sku gets dropped from the feed, and is reproduced and sent back over to SAS, SAS gives it a new product ID.

Hopefully this answer helps. Please let me know if you would like me to clarify further.

Thanks for the question. Please keep them coming!

Have a good one,

Brent

[Wayder]

Hi Brent,

Thanks, that is exactly what I was hoping for. I will align your SKU to be my unique identifier, this will solve that problem permanently.


Way...