Skip to main content
12-Amethyst
June 14, 2018
Question

enhancement request: make Component Occurrence accessable in js

  • June 14, 2018
  • 1 reply
  • 2619 views

In Creo View, you can click on a model and see the model attributes, like the part number.

If I want to use a Fuvoria Studio experience where the user can tap on a modelItem, I can manually set a text label to the part number of that modelItem. If the experience is larger than just a couple of modelItems, it's a lot of work to add the info to each individual modelItem.

We noticed that the Component Occurrence of each ModelItem matches the pathnames in Creo View.

It would be great if it was possible to auto create modelItems by means of the Component Occurrence path in the pvz. And if the name of the modelItem would be identical to this path, we could probably map the attributes of this part to the modelItem.

The result would be an experience where e.g. the service engineer would see disassembly sequences, but also the part numbers of each modelItem.

Regards,

Jaap

1 reply

16-Pearl
June 14, 2018

If you have a look at the model helicopter experience in the gallery, it does something just like this.  I've asked about it and it's using JS to read values from a JSON file that is setup and structured in a similar way to the PVZ file.

 

Studio recognises the structure as you can see when you create model items.  I think the ideal solution would be that the JS could just directly read the PVZ structure and attribute information contained in there.

 

 

jkramer12-AmethystAuthor
12-Amethyst
June 15, 2018

thnx!

I looked into the (zipped) contents of a random c3di-Creo Illustrate file. There's a file manifest.3di that contains the Component Occurrence and the name of the part. So, once we know the component occurrence, we could map the name to that 🙂

The contents of the sub-files in a pvz (ol and pvs) are compressed, so that doesn't seem to be an easy path...

Jaap