Skip to main content
L
LG_1009615414-Alexandrite
14-Alexandrite
July 12, 2023
Solved

Is it possible to mass create Problem Reports?

  • July 12, 2023
  • 2 replies
  • 1004 views

We have some legacy PR's in another tool and would like to mass create them in PDMLink.

They have some data that is only used in the legacy system so when we create a new PR those attribute fields for that data are not available (so unless we change the PR object we cannot manually create legacy PR with that legacy data).

 

Best answer by HelesicPetr

Hi @LG_10096154 

There are many ways how to achieve it.

 

You can use OOTB LoadFromFile function 

Here CS57369 is example how to use loadfrom file, in your case you use just ProblemReport 

 

csvmapfile.txt describes all supported method to load the data to a Windchill. Located for example in D:\Windchill_13.0\Windchill\loadFiles\

HelesicPetr_0-1689229946880.png

 

Another method is to write own custom function that read any type of input, xml, database, any source what you can read,  and you create exactly what you want in a Windchill. 

 

PetrH

 

 

 

2 replies

D
18-Opal
d_graham18-Opal
18-Opal
July 12, 2023

@LG_10096154 

 

Can you post sample data so that we know what the data looks like.

without seeing your data I’ll still go out on a limb and say YES, not a problem to write a utility that can read data and create Problem Reports.

 

David

 

 

HelesicPetr
22-Sapphire II
HelesicPetr22-Sapphire IIAnswer
22-Sapphire II
July 13, 2023

Hi @LG_10096154 

There are many ways how to achieve it.

 

You can use OOTB LoadFromFile function 

Here CS57369 is example how to use loadfrom file, in your case you use just ProblemReport 

 

csvmapfile.txt describes all supported method to load the data to a Windchill. Located for example in D:\Windchill_13.0\Windchill\loadFiles\

HelesicPetr_0-1689229946880.png

 

Another method is to write own custom function that read any type of input, xml, database, any source what you can read,  and you create exactly what you want in a Windchill. 

 

PetrH

 

 

 

Terms & ConditionsAccessibility statement