Serial Numbers + Item Names

Follow
Scott Melnyk

After years of using Flex, we're finally embarking on barcoding our inventory (yasssss).

We'd had accurate inventory counts, serial numbers, etc in place for a while. 

I recently changed the "item name" for some of our inventory, but when printing out our barcodes (using preferred.DisplayString), the old "item name" was printing.

Is there any reason why this would be happening? See below for an example.

Original "Item Name": QSC K12 Powered Speaker

We entered in all serial numbers when the item was called this

Updated "Item Name": Powered Speaker - QSC K12

When printing off barcodes of previously entered serial numbers, after the name update the barcode would read:

"QSC K12 Powered Speaker" NOT "Powered Speaker - QSC K12"

Thanks again for your help!

Scott

0

Comments

2 comments

Sort by Date Votes
  • Aaron Horn
    • Edited

    Scott, I would not have expected the result you're seeing since the Item Name lives with the parent model.  You may have to request Flex to do some sort of reindexing on the backend.  Either way, I think this is a support email.

    I use [element.shortName] for most of my barcode templates, but from another post, I believe you all use your naming fields a little differently.  But you could at least test with Short Name to see if you get the same undesirable result after making a change.

    Here's what you should expect when using the 2 typical mashup barcode fields:

    element.preferredDisplayString
    elements used = [Size] [Item Name] ([Stencil])
    example = 60" HD LED Display (TV61)

    element.name
    elements used = [Item Name] - [Size] ([Stencil])
    example = HD LED Display - 60" (TV61)

    Aaron Horn
    Consultant (endorsed by Flex)
    aaronjhorn@gmail.com
    615.335.1225

    0
    Comment actions Permalink
  • Scott Melnyk

    Thanks for the response, Aaron Horn - We got our naming fields all dialed in a way that satisfies our client facing / internal desires, which is great! 

    Good to know that this is a one-off for our flex system & not a deep seeded "oops". We've worked around the issue, but should it arise again, we'll contact support. Thanks for always being so quick to respond!

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post