Community Tip - You can change your system assigned username to something more personal in your community settings. X
Hi,
I have an problem about the table.
The user defined parameter can not displayed after i add some new code.
PIC 1
PIC 2
PIC 3
When i add the new code in PIC 3. The parameter (QTY1) can't correctly display after update table (see PIC 2)
I don't know what went wrong. There is no problem with the new code.
Solved! Go to Solution.
i use an other code instead of the NEW CODE in PIC3 which solved the problem of user defined parameter (QTY1 ) display.
Can you upload a sample file and state what version of Creo it was created in?
Please see attached for base code. I used another form of code to solve the problem.
CREO 4.0
@ZC_8293506 wrote:
Hi,
I have an problem about the table.
The user defined parameter can not displayed after i add some new code.
PIC 1
PIC 2
PIC 3
When i add the new code in PIC 3. The parameter (QTY1) can't correctly display after update table (see PIC 2)
I don't know what went wrong. There is no problem with the new code.
Hi,
look at base code ... endif command is missing at the end of first if command.
Sorry, i deleted the ENDIF in PIC 3 by accident which made the code looks have some bug. But the lack of ENDIF does not exist in the base code.
Please see attached for base code. I used another form of code to solve the problem.
Looks like you're missing an 'ENDIF'.
Sorry, i deleted the ENDIF in PIC 3 by accident which made the code looks have some bugs. But the lack of ENDIF does not exist in the base code.
Relation as in image may help....
EDIT: If this doesn't work, share a sample file and replace the report parameter asm_mbr_name with asm_mbr_part_number or as per your use case with appropriate values.
Thank you for your new idea !
But it look like another user defined parameter "AAA" can't display correctly. Creo4.0 is strange😂
The error also exist in your screenshot
i use an other code instead of the NEW CODE in PIC3 which solved the problem of user defined parameter (QTY1 ) display.
Of course . I don't know what's wrong with the code (in PIC3) I added before. But they do cause the display error. 😰