web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics RMS (Archived) / ItemLookUp versus Alia...
Microsoft Dynamics RMS (Archived)

ItemLookUp versus Alias - which has precedence? (UPC-->EAN transition)

(0) ShareShare
ReportReport
Posted on by Community Member

We have a manufacturer who switched all their products from UPC barcodes to EAN barcodes.

They are only providing pricing update files with EAN numbers and no UPCs.

Many products are in our database twice. Once with the UPC (older stock) as the ItemLookUp and once with the EAN (newer stock) as the ItemLookUp.

We want to scan a (older stock) product's UPC number and still get the current/new pricing.

If, for each EAN product, we load in an alias that's the old UPC number, will RMS pull up the old product with that number as the ItemLookUp or will it pull up the newer product with the alias?

It's a bit messy, we'd have a DB record with "12345" as the ItemLookUp and a second DB record with "12345" as an alias.

The universe might explode. Unless it's documented and known, it's a recipe for trouble.

Anyone know? Or any elegant solution that I'm missing?

Thanks!

*This post is locked for comments

I have the same question (0)
  • ALT Profile Picture
    ALT 5 on at
    RE: ItemLookUp versus Alias - which has precedence? (UPC-->EAN transition)

     RMS will not allow you to do this.   Change the old Itemlookupcode to 12345-OLD and add the old itemlookupcode 12345 as an alias to the new item.

  • Community Member Profile Picture
    Community Member on at
    RE: ItemLookUp versus Alias - which has precedence? (UPC-->EAN transition)

    How block editing itemlookupcode field en Dynamics RMS in Mode Manteninance.

  • Suggested answer
    Community Member Profile Picture
    Community Member on at
    RE: ItemLookUp versus Alias - which has precedence? (UPC-->EAN transition)

    RMS uses the itemlookupcode first,  then scans aliases,  then matrix items.  

    This is done all within the same query with sql indexes,  so you might see differences sometimes.  

    you could do a table update.

    update item set itemlookupcode = ItemLookupCode + 'OLD' where ItemLookupCode in (select Alias from Alias)

    this appends old to any itemlookupcode that also exists in the alias table as an alias.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics RMS (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans