Mike Lockwood wrote:
Couple of thoughts.
1. Make sure that these documents are "Reference Document" or a created sub type of them - such that the Revision of the Document which is retrieved with a WTPart is the latest Rev (Reference relationship to WTPart floats to latest - RELEASED state or as configured).
Mike: What are your thoughts on setting the preference "Part to Document Association Logic" to Yes to allow non Reference Documents to be added as a Reference Document?
Hello,
I'm working with 11 F000, MPMLink, and ESI to publish Process Plans to SAP. When Windchill generates the ESI Response, it only includes newly created reference document links to process plan operations. In other words, if a reference document existed prior to changing the operation, or is removed from an operation, no link is published. Therefore, ESI is not removing the link, and the document PRT references become additive on the SAP side.
I did find a preference to render unchanged objects, but then it publishes all documents with a create link and adds multiple links on the SAP side.
I've filed a support request, but thought I'd reach out to the community for any experience with this issue.
Does anyone successfully publish PRT document links to routing operations in SAP AND remove them on changes? If so, what am I missing?
Thanks,
Casey
Important decision to set this preference as stated - that to me, seems to throw away very useful functionality. Even if not useful at the moment, may be very useful to the organization at some future time.
Mike Lockwood wrote:
Important decision to set this preference as stated - that to me, seems to throw away very useful functionality. Even if not useful at the moment, may be very useful to the organization at some future time.
My understanding of this preference "Part to Document Association Logic" = Yes will only change what type of documents can be added as a Reference Document link. It will NOT change how that Reference Document link is handled. So to me what you would lose is the ability to easily search Windchill for documents that could be used as a Reference Document link. Because you couldn't simply search for all documents of type Reference Document (or subtype). You would not lose the functionality of a Reference Document link.
Am I missing something important here? We haven't started using these yet however are close and I would like to know if I am missing out on something here.
Thanks Randy
Good point, I stand corrected.
But, if at any future time, you reverse the preference, the documents returned may not be as expected.
Hello,
We use SAP for repair operations on customer equipment within the SAP Customer Service (CS) Module. The "Router" used for this is functionally very similar to a standard production Router used in Production Planning (PP), but not the same object. We are implementing ESI for standard production routings and are also interested in managing repair routings in Windchill.
However, this is not supported in OOTB MPMLink/ESI, so we are pursuing this development.
Has anyone gone down this road and would you be willing to share lessons learned?
Thanks,
Casey
Edit: Used proper explanation from PTC instead
"Once importable spreadsheets have been created, they can be imported using the “Import from Spreadsheet” action available on the Action menu of the desired Product or Library.
You can import part and product structure data from a Microsoft Excel spreadsheet into a library or product. Importing allows you to build product structures from existing parts, create new parts, or update existing parts using data in the import spreadsheet.
You can import the following types of data:
- New parts or modifications to existing parts.
- A new bill of materials (BOM) or modifications to an existing BOM.
When you export parts or product structures from Microsoft Excel to Windchill
PDMLink, consider the following:
- You can import a spreadsheet with multiple worksheets.
- In Row 1, the first cell contains a string that defines the type of data to be imported:
- Rows 2 through 5 of each worksheet are reserved for comments. If you previously exported the spreadsheet from Windchill PDMlink, row 5 may contain logical IDs for the attributes included in the spreadsheet.
- Row 6 contains column headers.
- Rows greater than or equal to 7 contain the data to be imported.
- The order of columns in the spreadsheet is not fixed.
- If you want to exclude one or more worksheets from import, leave the first cell of the worksheet empty or change the value for ImportSheetType, for example, set it to ImportSheetType=NONE. A worksheet that does not list the correct value (PART, AXL, or BOM) will be excluded on import."
Scott Morris is there anyway to split this from the assumed-answered original discussion? It deserves its own thread.
The original question was how to perform a bulk rename in Windchill; Devidas is asking about exporting an object list which can be accomplished by creating a search within that context and the search results window has a Save-As (I think, maybe Export, check the drop down menus for the results table) that allows creating CVS, Text, Excel, output. The search results may need a custom view to be created depending on the desired information.
In any case, the key to exporting the list is that it's a function of the Search results, not the folder contents display.
It is frustrating that the non-search windows haven't allowed Select-All, Copy to easily transfer tabular data, but there it is.
Hi,
From the provided screen shot, it is difficult to know the actual root cause as there may be other factors. Can you please provide me below details?
1. Windchill Server Version
2. WWGM Client Version
3. CEDM Version with maintenance level
4. Does the client system consist more than one version of CEDM installed? If yes, its version.
If we are not able to find out the root cause, then I would suggest you to contact PTC Tech Support for further assistance as it may require to have some debug logs to find out the issue on your system.
Regards,
Pankaj Mooteri
Unfortunately, I don't have those types of permissions in this community, maybe Toby Metcalf can make the split for you.
Regarding the question, there is a way to add standard export actions to tables in Windchill. When I was the ProjectLink guy, we implemented it for the Plan table and documented it in the Windchill Customizer's Guide under the topic named "Adding Export Functionality in the Project Plan Table". Those pages are attached for quick reference.
My assumption is the same capability should be available in the core ui, but I am not sure which XML file controls the various folder browser tables.
PTC implemented some of these actions on the Academic Windchill server used by students in the FIRST, RWDC and Formula SAE programs as shown below.
They are also available in the Discussions table of a Project container.
Hi David, Scott Morris is right - I am happy to help move content and will be in touch.
Toby
can someone explain what is the down side of leaving the state to "in work" for all the file if we are not using change management at this time.
It allows your engineers to change a 'released' drawing/model.
Even if you don't do CM through Windchill, you should still have different states for the lifecycle of the parts. When a design is released, the state should be set to 'Release' to prevent further changes to that revision. When a change is needed, the engineer can do a revise to the part and set it to the next revision. Leaving all files at 'In Work' does not protect the system or your data. This also requires your company to set up proper ACLs for data management within Windchill.
Engineers may read or revise a released document, but not modify it.
Engineers may have full control to an In Work document or you may limit them to modify. Full control would give them delete, set state and revise along with other permissions they do not need.
I would say so you can lock down the design, especially at certain mile stones. Otherwise if someone makes a change and you can never go back and get to the state you wanted the design without a ton of manual work.
It's all too easy if you use states and revisions to add to your workspace the correct revision and/or state of an object. If everything is at initial revision and in work you might have to sift through hundreds of iterations of a part to find the version you want.
A co-worker's search is fixed to CN's and if wants to search for other object Types he must always change the "Type" to "All". Starting with Windchill 10.0 this was supposed to be standard operation (last options selected, selected on next search). Any ideas what may be wrong?
Did they change the user preferences by mistake?
No, they did not even know they had preferences . But, we noticed their search types is locked. Mine is not locked. I can only assume this is the cause of the issue.
We would like to export all of our Creo parts, and Assemblies, out of Intralink 10.0 M30. Is there a way to automate this process, or do we need to checkout the files to a workspace and do it manually?
Thanks,
Rob
Dear members,
I have the same problem that Patel, have two DNS configured, one for the address of the Reverse Proxy (external access) and another for the host machine (internal access). External access works perfectly. However, on internal access, when I enter the host address, and after adding user and password, the system redirects me to the external address. How do I remove this redirect? I need internal access to be maintained with the host address.
Thanks
Hello,
we use:
Windchill 10.2
WGM M030 CPS 18
Modeling 19.0 M040
On the same PC there is Modeling and Drafting not in differrent
releases installed
Local supports tells me "Unattended Installation" is not supported.
How can I manually install more than 200 Clients ?