nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Push Computed Field to Windchill RV&S Relationship

medini_1077175841

Our current goal is to compute a relationship/field in Medini Analyze that connects functional and safety requirements and push that field to a relationship/trace in Windchill RV&S. I have written a two scripts for two computed fields, the first is a list of the requirements in Medini Analyze, the second is a string comprised of comma-separated IDs that can be used in Windchill RV&S. This method will be push only.

When I was looking the the logs of the Windchill commands that are being run by Analyze, I noticed that none of the calls were related to this field that I am trying to push.

I would expect the program to run something like "im editissue --field="Is Related To"=123123,123124 123125"

This command works as intended from the command line.

Attached: An image of the computed fields, an image of the expected command working on the command line, and the mapping file we are currently using (the related line is at the bottom).

Thank you for the help.

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Hi Logan,

looks all good to me to be frank. I assume you do not get any error or warning when pushing?

Could you try to remove the direction="out" temporary and push?

I also asume you have enabled some integrity debugging to see the executed commands on the console?

Jan

medini_1077175841

Hey Jan,

I am not getting errors or warnings when pushing, everything is considered "Successful".

I attempted to remove the 'direction="out"' and noticed no change.

As far as integrity debugging, I have enabled it and am attaching to this response the log that was generated.

If you have any other ideas I am game to keep working through them, sort of at a loss as to why I am both getting no errors, and nothing happening.

Thanks again!

medini_1024169437

Hi Logan,

hm, difficult case indeed. I have no real idea and would need to replicate it here. Once thing I noticed when looking at the log. It seems there are two fiels with the similar name, the second has a single quote at the end? That looked a little strange, though surely is not the root cause.

Whats the type of the field on PTC side? Just to replicate that.

Regards

Jan

medini_1024169437

Logan, some update: I tried to replicate your scenario (reading from a custom, scripted profile property and writing into a text property in PTC) and it worked for me.

Maybe you can compare,

- I used JavaScript, not OCL or others, I returned a single string

- the target property in PTC is of type shorttext

- I see the actual im command in the PTC log

Jan

medini_1077175841

So the only difference I see between our scenarios is that the target property in PTC is a field of type "Relationship" (I will attach the output of IM viewfield for you). I am using Javascript for calculating the field.

And I cannot remember why we have the two fields Is Related To and Is Related To', but I am only interested in setting the first one for now.

So the struggle here is updating a relationship in PTC from a calculated "field" in Medini (I am fine with this calculated field being of any type).

Thank you for your time!

medini_1024169437

Hi Logan,

I dont think that this is posisble at the moment, so the integration is able to map medini relations to integrity/windchill relations , but you cant map text 8or a list of string ids) to a list of items in PTC.

What worked in my place was to write the comma separated text (result of the computation) to a tetx field in PTC. I think tahts also true if your script would return a list of medini objects, rather than teir ids, the mapping would ot work, I am sorry.

Regards

Jan

medini_1077175841

Thanks for the all the help, I will consider this resolved for now and look for another way to solve this issue.