cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Repeat Region Table Filters...continue on next line?

Re: Repeat Region Table Filters...continue on next line?

Highlighted

Re: Repeat Region Table Filters...continue on next line?

The only thing I can think of, and I admit I kind of hate it, is to have an additional parameter in the parts, something like "useInTable" which is a boolean (Y/N) parameter. This seems nice, but the part I hate is I'd then have to add a relation to all the parts which determines the boolean value based on the part's DESCRIPTION. Why don't I like it?

(1) I've gotta jump into all the parts to add the parameter and the relations.

(2) I don't know what will happen if there are parts that don't have the given parameter - will the table fail? Experiments or advice from someone who has done this type of thing are needed.

(3) If I later find I need another criteria to be used, like I want to add "VALVE" to the okay descriptions, I would have to revisit all the parts and update the relations.

So, as implied, not an elegant solution, more akin to using a brick as a hammer, but it might work.

Re: Repeat Region Table Filters...continue on next line?


@KenFarley wrote:

The only thing I can think of, and I admit I kind of hate it, is to have an additional parameter in the parts, something like "useInTable" which is a boolean (Y/N) parameter. This seems nice, but the part I hate is I'd then have to add a relation to all the parts which determines the boolean value based on the part's DESCRIPTION. Why don't I like it?

(1) I've gotta jump into all the parts to add the parameter and the relations.

(2) I don't know what will happen if there are parts that don't have the given parameter - will the table fail? Experiments or advice from someone who has done this type of thing are needed.

(3) If I later find I need another criteria to be used, like I want to add "VALVE" to the okay descriptions, I would have to revisit all the parts and update the relations.

So, as implied, not an elegant solution, more akin to using a brick as a hammer, but it might work.


Hi,

maybe using component parameter is the right solution. In this case user do not have to modify models, parameters are saved in assembly, only.

To make it easier to fill component parameter with specific value, user can develop auxiliary application which reads filtering conditions and assigns appropriate value.

 


Martin Hanák

Re: Repeat Region Table Filters...continue on next line?

I know you're not excited about it, but I still think repeat region relations are the cleaner solution.  Everything is contained in one place, the're very easy to write, and you don't have to make any changes to the existing parts or assemblies.  @MartinHanak gave a good example of how to do this here.  Let me know if you need an example created for your actual conditions.

Re: Repeat Region Table Filters...continue on next line?

I was going to try and use the relations but then I remember why I abandoned it.  It gets much more complicated trying to handle wild cards.  E.g. *P*SEAL.  I think it could be done using 2 different searches then comparing where they occur relative to one another, then returning a result based on this.  However this would have to be done for each criteria and I think can get complicated fast.

Re: Repeat Region Table Filters...continue on next line?

@MartinHanak, I don't think I understand your suggestion.  I am not sure how/where to modify component parameters if not in the component models.  I know no other way of doing this.  Also I am not sure what you mean by an auxiliary application.  Can you explain a little more for me?  Thanks!

Re: Repeat Region Table Filters...continue on next line?

At this point I don't think it is worth it to modify all our components to add a parameter.  This is a challenge with change state control and checking in/out.  Unless I misunderstood you, for our situation and the number of parts we have, I think the medicine would be worse than the sickness! 🙂  

Re: Repeat Region Table Filters...continue on next line?


@lscheeler wrote:

@MartinHanak, I don't think I understand your suggestion.  I am not sure how/where to modify component parameters if not in the component models.  I know no other way of doing this.  Also I am not sure what you mean by an auxiliary application.  Can you explain a little more for me?  Thanks!


Hi,

in attached rr_2019-11-21.zip (Creo 2.0 files) you can find example of component parameter.

modeltree.png

  • DESCRIPTION ... part parameter, saved in part file
  • cpar1 ... component parameter, saved in assembly file

partpar.png

comppar.png

 

If requested functionality is not available in Creo, user can develop "auxiliary application" using programming API (Toolkit, J-Link, VB). In your case the app could:

  • cycle through list of all components
  • for every component read DESCRIPTION value, check the rule and set CPAR1 value to Y (if rule is satisfied, otherwise set N)

Then you will be able to filter repeat region using single parameter ... CPAR1


Martin Hanák
Announcements
LiveWorx Call For Papers Happening Now!