Skip to main content
L
LawrenceS18-Opal
18-Opal
November 19, 2019
Question

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

  • November 19, 2019
  • 4 replies
  • 5965 views

I am getting an error because evidently there is too many characters on one line for an OR statement in the repeat region table filters.  Does anyone know how to continue on next line or another work around? E.g.

  • &asm.mbr.DESCRIPTION==*O-RING*,*BACK*UP*,*D*RING*,*SOLO*SEAL*,*PAR*BA*,*D*SEAL*

The above line is an example of too many characters on one line and Creo not accepting it...even after I delete the spaces (which oddly helps even though Creo will put the spaces back in when you hit ok...very fickle).

 

It would also be nice if we could do OR statements for different parameters...but maybe that is asking too much. E.g.

  • &asm.mbr.name == 600*,&asm.mbr.DESCRIPTION==*o-ring*,*back*up*ring*

4 replies

T
23-Emerald IV
TomU23-Emerald IV
23-Emerald IV
November 19, 2019

Do you have active maintenance?  I'm willing to create a support case and ask if you don't...

L
LawrenceS18-OpalAuthor
18-Opal
November 20, 2019

I appreciate that @TomU, thank you!  Unfortunately I did open a case back in February, 2019 and they said that it was not possible ("Works to product specification" 😖), nor did they provide a usable workaround.  However, I thought I would through it out on the forum because I have seen PTC not be able to answer something but the users find better workarounds.  In this case it appears there may be no decent workaround.

K
KenFarley21-Topaz II
21-Topaz II
November 20, 2019

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.

    M
    Mahesh_Sharma22-Sapphire I
    22-Sapphire I
    November 19, 2019

    @LawrenceS 

    As per current limitations for application 80 is the character limit for a line. Exceeding the limit will report error about line 2. 

     

    Existing Idea : https://community.ptc.com/t5/Creo-Parametric-Ideas/character-limits-for-parameter-values-CS32012/idi-p/454577

     

    EDIT: Having parameters in 2 different lines, as illustrated below, seems to work.

    &asm.mbr.name == Cylinder,crankshaft
    &asm.mbr.name == ENG_BLOCK_REAR, ENG_BEARING, ENG_BLOCK_FRONT

    T
    23-Emerald IV
    TomU23-Emerald IV
    23-Emerald IV
    November 19, 2019

    @Mahesh_Sharma, 

    Is there any type of line continuation character that will work for repeat region filters?

    M
    Mahesh_Sharma22-Sapphire I
    22-Sapphire I
    November 19, 2019

    I don't think so.. 

    B
    23-Emerald III
    BenLoosli23-Emerald III
    23-Emerald III
    November 19, 2019

    I am not seeing what it is that you are asking for.

    Your line:

    &asm.mbr.DESCRIPTION==*O-RING*,*BACK*UP*,*D*RING*,*SOLO*SEAL*,*PAR*BA*,*D*SEAL*

    Only contains 58 characters to be assigned to the Description parameter.

     

    Are you trying to do an IF-Else type of Description?

    Give an example of what your final output should look like and your proposed input to drive those results.

     

    T
    23-Emerald IV
    TomU23-Emerald IV
    23-Emerald IV
    November 19, 2019

    @LawrenceS made additional comments here:  https://community.ptc.com/t5/Assembly-Design/Filter-Repeat-Region-by-Two-Conditions/m-p/636830#M20176

    T
    23-Emerald IV
    TomU23-Emerald IV
    23-Emerald IV
    November 20, 2019

    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.

      L
      LawrenceS18-OpalAuthor
      18-Opal
      November 21, 2019

      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.

      Terms & ConditionsCookie settingsAccessibility statement