Why attachment is getting stored on ZZ_YYsc_cart_item not on ZZ_YYsc_req_item.

karun006
Tera Contributor

Why attachment is getting stored on ZZ_YYsc_cart_item not on ZZ_YYsc_req_item.Why attachemtn type variable is storing attachment on ZZ_YYsc_cart_item how to get it solve set to ZZ_YYsc_req_item table.

7 REPLIES 7

Sebastian L
Mega Sage

Hi, the ZZ_YY is a prefix added, so it does not show on the top of the form. I suspect you have an attachment variable, and then this is expected behaviour. Usually when it is on sc_cart_item it is a temporary attachment, that then gets stored correctly when the item is created. 

 

If this happens after submit of the item, then the table should be corrected, but the prefix of ZZ_YY will still be there. You can follow this thread if you wish to add it to the top of the item: https://www.servicenow.com/community/now-platform-forum/disable-zz-yy-prefix-from-attachment-when-ad... 


Best regards,
Sebastian Laursen

Thank you so much for replying i have put this solution and its working but not on prod because on other instance it is storing attachment on   "zz_yysc_req_item" BUT ON PROD ITS IS string it to "ZZ_YYsc_cart_item".

Which is not letting the table name update. Any idea why it is sharing data on ZZ_YYsc_cart_item table not on ritm table?

Can you check if property "glide.sc.enable_order_now" is set to true in prod? (https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0961833)

 

Otherwise the last thing I could find was about having a current.update() in a business rule on sc_req_item, but it is a very old, but maybe if the above can't help locate the issue, then this might: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0725630 


Best regards,
Sebastian Laursen

I am having the same issue mentioned in this post. I am unable to open that KB article even though I am logged in. I noticed that the attachment variable is storing on ZZ_YYsc_cart_item when ordered in the portal, but gets stored properly on ZZ_YYsc_req_item when ordered in the native catalog view. Any solution for this?