cancel
Showing results for 
Search instead for 
Did you mean: 

PD 16.6 and problems with FindChildByCode()

former_member217396
Participant
0 Kudos

Hi all,

does anyone have issues using FindChildByCode() in the PD 16.6? All out Extensions/Script using FindChildByCode() are not working after the migration to PD 16.6.

BR,

Rafal

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member217396
Participant
0 Kudos

Problem solved

In 16.6 you have to use:

FindChildByCode("00_MASTER", PdPDM.cls_User)

instead of

FindChildByCode("00_MASTER", cls_User)

Former Member
0 Kudos

Hi Rafal,

I think, that using the library prefix is correct approach in this case. Your previous syntax (just cls_User without library prefix) might work in unambiguous cases, like for example cls_Table. This object is only in PDM. But the object User is present in more than one libraries: RMG, RQM, ILM and PDM).

So if you don`t want to examine each object type separately and make your scripts less vulnerable to PD upgrades, I suggest you to use the library prefix each time.

Ondrej

P.S. Your post led me to idea to start a discussion about the complete list of changes in API. You can check here: