Spaces at the front or end of Product IDs or Descriptions

Hi,
One of my biggest bugbears since using Pimberly is that when loading Product IDs and Descriptions, the system allows spaces at the beginning or end of the field.

Like most people, our users and suppliers are human. Despite our best efforts to check, we still see Product IDs and Descriptions slipping through with spaces at either end.

It would be really helpful if, within the Schema, you could set a rule for the Product ID field such as:

  • Allow spaces in Product ID
  • Do not allow spaces at the beginning or end of Product ID
  • Do not allow any spaces

And similarly for Descriptions:

  • Allow spaces in Description
  • Do not allow spaces at the beginning or end of Description
  • Do not allow any spaces (Not sure this one would have many takers, but it would cover every possibility.)

If the data is being uploaded and the Product ID or Description does not meet the selected criteria, that line should not be uploaded.

If the data is being manually input and the Product ID or Description does not meet the criteria, a warning should be triggered either when exiting the field or upon saving the record.

This small change would prevent the frustration of stray spaces being sent to back-office systems and websites, and the subsequent work required to correct them across downstream systems.

If you have any thoughts, I’d love to hear them.

2

Comments

1 comment
Date Votes

Please sign in to leave a comment.

  • Great idea, I too have fallen foul of these things in the past, especially the trailing ones. It would be great to be able to define something like a regular expression to these key attributes like we can on a "Code" attribute.

    Maybe the Identifier format will help with the product ID, its been a while ago and I can't remember if a blank space is classed as a "Symbol" or not but if it is you might be able to explore changing over to "Letters and Numbers".

    As for stripping blank spaces, no suggestion outside of pre-cleaning before it gets loaded but to expand on my regular expression contribution, being able to set a regex pattern as the match criteria would be nice for some of the "replace" type expressions.

     

    0

Didn't find what you were looking for?

New post