Working with the existing LU EngPartRevision, we added some custom fields to extend the LU in a centralized testing environment. After standing up a new development environment, we created the custom fields by exporting an Application Configuration Package (ACP) and importing it into the new environment. The fields validated and imported into an Approved state. When I attempt to publish and synchronize the custom fields, I receive the error “COMPILE_ERROR2: Error during compilation of LU [EngPartRevision]” that looks like it is related to extended the custom view (CFV).
Hello Community,We are migrating engineering part information into an existing implementation and have a need to create separate engineering part structures and hierarchies that utilize the same components. For instance, Parts A and B may both utilize Part C as a child component, but the Part B hierarchy would have further children parts that Part A would not have. What we do not want is when looking at the structure and hierarchy for Part A, to see the child components related to Part B. Further, we do not want modifications made to a parent/child to affect the structure of another part. Is this supported in Apps10, and if so, is there a recommended practice to implement this? Looking at the engineering part structure data, it seems like this may be possible by delineating a structure ID, but I can’t find how to set that on the front end or through the migration documentation.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
