Anyone using Desktop Integration with property mapping? We are interested in using it to make Word documents like "smart" Pro/E drawing formats.
From what I tried, we're missing something on the mechanism for refreshing attribute values - see attached. Note: To see the codes in Word, toggle Field Codes on / off.
No reply on this yet from tech support. We'd really like to use this - hoping that the content of the Word file that you download is not dependent on having DTI on each machine used for download - but that's secondary to getting it to update attribute values at all.
Have you found solutions on mapping Windchill attributes to Ms Office document properties?
I'm trying to implement DTI as well, based on MS Office 2003. But the mapping isn't OK. If I interpret it correctly, your example isn't either. E.g., how do you retrieve the 'last modify date' or the 'modified by' attributes in Word?
I haven't logged a call yet, but will do shortly.
<< ProE WF3 M230 - PDMLink9.1 M050 >>
we have a lot of MS Office files managed in PDMLink and we map the PDMLink attributes. As always we had surprises at the beginning but now it is working very well.
There are some client configuration. For instance in installing Windchill Desktop Integration even for the users who only read the file because in order to update/map the attribute one must use Windchill Desktop Integration as the Download Mechanism . The option for the download Mechanism is available in the user preferences/Attachment.
All the system attributes are not available for mapping but most of them are sometimes in weird name. For instance Description in PDMLink is Comment in Word. All our soft attributes are also available for mapping. Word is actually easy to do. excel a bit more tricky but it is not possible to map anything with Powerpoint.
I have attached some internal documentation + some I got from people who helped me in the past.
Hope this helps, otherwise let me know see if I can be of further help
You mentioned the use of updating attributes via Productview. As was mentioned, it requires the DTI client on the user's end to process the updating of the attributes in the native doc. All Productview is doing is opening the static representation (PDF most likely) that has that attribute data captured as of the point in time the rep was made. Your doc worker will be using the DTI functionality on the back end when the rep is being made.
Hi Mike @MikeLockwood
Just wondering, 11 years later, are your still using DTI and what do you think of it.
From my side, back in 2009, it had become the standard for all MS Office files checked in to Windchill. We had WTDoc templates including subtypes and the more linkages with attributes the better.
Over the years I have worked in different companies, some working with other PLM systems but having the same type of functionalities and I was always surprised to see that many admin did not even know what they could do with such functionalities. While I find it so powerful.
It is a shame though that Powerpoint still can't be integrated the same way as far as I know.
What about you @HugoHermans ?
Microsoft still does not support Document Properties in Powerpoint, that is why there is no integration. I am always shocked with each new release that does not contain this critical capability.
Hello and thanks for reaching out.
At previous company, we had DTI in use fairly extensively and all worked well.
At current company, we're not yet managing non-CAD in Windchill (long story), so it hasn't been part of the mix to date.
I'm personally out of date on DTI functionality after 10.2 - interested in catching up 12.x.
Good to hear from you Mike,
My take is that PTC is doing the opposite of what they tell their customer ie product consolidation and they spread their energy and project in all sorts of initiatives and many functionalities are no longer under the radar aka no longer further developed. For instance projectlink, after 10 years it still has not become a true project management system. Integrity still looks as if it is a 3rd party software, Product Configuration, still very limited in what the interface can provide. and the list goes on. However. I am out topic...