Stop "Import" Script Step from being considered for "Unreferenced"
I have a Script with a Step "Import." It has "matching names" checked so that any future Fields that match will be included. It has all Fields in the Table selected for import because it imports from a Clone so all enterable Fields are included. I do not consider this Script Step as used to determine if a Field is unreferenced in the DB.
I would like to have some way to not have this Script Step be used in determining if a Field is unreferenced or not. Below is the reasoning...
Importing is just automated keyboard input, so if a Field is only used via an Import Script Step and no where else (not a Layout Object), the Field really isn't used or ever displayed. There is no reason why I would want to import a Field and then never display it or use it.
Perhaps this could be a user-preference checkbox to disallow the above condition from being considered referenced.
Steven
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Nicholas Orr on 09 Mar, 2011 12:04 PM
Steven,
Thanks for this. There is actually some code, new to v3 that was meant to record the import item reference but not make it count towards the total. It turned out to have a bug, but I've fixed this in my current dev version, so it will be in the next update. I can send you a copy if you'd like.
Cheers,
Nick
Nicholas Orr closed this discussion on 20 Dec, 2011 12:40 AM.