• Locked Locked
  • Replies 0 replies
  • Subscribers 4 subscribers
  • Views 1416 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SUPPORT Q&A - Filter Value, label or value field length

Archive User
オフライン

Ron - Tuesday, December 14, 2010 11:06 AM:

I am using filter lists to help build the part names, at least start building the name for the users. I have my part form working with four filter list which are used to select the type of component. Based on the what the user selects I would like to have the Name field be populated with a pre-defined text such as when the user is entering for a connector the default required info would be
“[Category]  [Name]  [Positions]  [Rows]  [Max current]  [Gender] [Insulated]  [Hole dia]  [Wire gauge] “
 
I would like to use filter values for this, but the default label or value field length is set to 64 for itemtype Filter Value, I thought I would just increase the length to something like 140. Logged in with admin rights I see that I would need Root account rights to modify this itemtype. So before doing so I thought I would post this on the form. Is there a reason why I cannot increase the length to 140 for item type Filter Value?

Brian - Wednesday, December 15, 2010 6:36 AM:

Hi Ron,

I can't imagine any reason why you can't change the field length. Like most things in Innovator the field will be applied to things but the lengths don't seem to matter.

You can't change it with Admin simply because it is part of the "core" solution.

It is possible that changing these core items could be overridden by an upgrade. May have to watch out for that.

You could create a new Item type to hold the default part information and have the list trigger a lookup into that item type. That way you are not limited by the field size.

Cheers,

Brian.


Ron - Wednesday, December 15, 2010 9:11 AM:

Thanks for the reply Brian, I was trying to do just that, but it was not working the way I would like and it's getting messy with yet another field I would have to maintain. just extending the existing label/value field length would work best. Since it was a core component I was a little hesitant in modifying it. I agree it might cause an issue in doing the next upgrade, therefore I will log this change in my records.

 

Thanks Again

 

Ron

Copyright © 2025 Aras. All rights reserved.