repeat region filter limited to 80 characters

[Nicolas_G]

Hello,

I have a filter condition which exceed the limit of 80 characters. (&asm.mbr.name==...)

The opposite condition doesn't result in a shorter formula.

I tried to use "or" ( | ) but didn't success.

&asm.mbr.name == *val1*, *val2*, *val3*,...

|asm.mbr.name == *val11*, *val12*, *val13*

Do you know a solution ?

Thanks.

[MartinHanak]

Hi,

discuss your problem with PTC Support.

[KenFarley]

You have not specified what version of Creo you are using, so perhaps the repeat relation functionality has changed since Creo 4.0.

Either way, maybe the following (extracted from a pertinent article, CS150475) may be informative:

How to write a repeat region relation that uses a wildcard in Creo Parametric

Applies To

• Pro/ENGINEER and Creo Elements/Pro Wildfire 2.0 to Wildfire 5.0
• Creo Parametric 1.0 to 4.0

Description

• How to write a repeat region relation that uses a wildcard
• It always gets the wrong result when add a relation in repeat region

Cause

The wildcard (*,?) cannot be used in relation

Resolution

• Not part of the Pro/ENGINEER, Creo Elements/Pro and Creo Parametric functionality
• Workaround:
  • Use function extract(string, position, length) instead of the wildcard
  • For example:

If write the relation as below, you will get the wrong result:

If asm_mbr_name=="X*"
A=1
else
A=2
endif

If write the relation as below, you will get the correct result:

Y=extract(asm_mbr_name,1,1)
if Y=="X"
A=1
else
A=2
endif

[BenLoosli]

Give us a better description of what you are doing with the relation?

Relations have always been limited to 80 characters.

[MartinHanak]

---

@BenLoosli wrote:

Give us a better description of what you are doing with the relation?

Relations have always been limited to 80 characters.

---

Hi,

I think OP needs something like

&asm.mbr.name == *val1*, *val2*, *val3*, *val4*, *val5*, *val6*, *val7*, *val8*, *val9*, *vala*, *valb*, *valc*, *vald*, *vale*, *valf*, *valg*, *valh*

Length of this line is 152 characters. It exceeds 80 characters limit.

[Nicolas_G]

Hello @BenLoosli ,

@MartinHanak his right. 

I have to write a relation like that: 

&asm.mbr.name == *val1*, *val2*, *val3*, *val4*, *val5*, *val6*, *val7*, *val8*, *val9*, *vala*, *valb*, *valc*, *vald*, *vale*, *valf*, *valg*, *valh

But it exceed the limit of 80 characters.

Best regards,

Nicolas

[MartinHanak]

---

@Nicolas_G wrote:

Hello @BenLoosli ,

@MartinHanak his right. 

I have to write a relation like that: 

&asm.mbr.name == *val1*, *val2*, *val3*, *val4*, *val5*, *val6*, *val7*, *val8*, *val9*, *vala*, *valb*, *valc*, *vald*, *vale*, *valf*, *valg*, *valh

But it exceed the limit of 80 characters.

Best regards,

Nicolas

---

Hi,

you can use procedure similar to the following one:

Define repeat region relations

Define filter

The above mentioned settings are used in uploaded Creo 4.0 drawing.

[Nicolas_G]

Hi,

Thanks for the proposal Martin,

But use relations instead of filter cause another issue.

Additionnaly I have to change the index number for this region.

For that I add the relation:

at table creation it works fine:

When I fix index, The index is well updated  and reordered but the relation ITEM=400+rpt_index is not re calculated.

for example I changed index 3 to 1

Is there a solution to force the relation to be calculated or to add all the values (over than 80 characters) in filter ?

Thanks,

Nicolas Guillot

[MartinHanak]

---

@Nicolas_G wrote:

Hi,

Thanks for the proposal Martin,

But use relations instead of filter cause another issue.

Additionnaly I have to change the index number for this region.

For that I add the relation:

at table creation it works fine:

When I fix index, The index is well updated  and reordered but the relation ITEM=400+rpt_index is not re calculated.

for example I changed index 3 to 1

Is there a solution to force the relation to be calculated or to add all the values (over than 80 characters) in filter ?

Thanks,

Nicolas Guillot

---

Hi,

unfortunately your questions are too complicated for me. Please ask PTC Support directly.