Autovue is a windows  application ported to Linux so there used to be some features (PDF generation?)  that weren’t available on the Linux port, Otherwise I don’t think there is much difference. We use linux as that what we have most experience supporting as an OS for servers.

If it were me I’d choose based on what support skills you have unless those missing features on linux autovue is critical to your business

You might be able to do it a privilege, allowing only read BoM table items not in Obsolete.  User would just get grey line showing something is there but not revealing the detail.

Nick,

Oracle don’t publish the database schema for Agile, so I expect Kevin has just done the graft to figure out the relationships between tables. As you will have seen from their naming most table do what they say in their name. As you are finding there are a few key tables where you need to look to relate an ID to a meaningful value.

Now given you have mentioned the magic word ‘Motorcycle’  which manufacturer do you work for and what discounts are available for the help tendered so far 😉

Adrian

change_in is the id of the change in the table change, so you would need another join like

join agile.change C on agile.bom.changes_in = c.id

Then select the fields from the change table you want your query to return. 

Repeat for change_out

This works for me….

select LE.ENTRYVALUE from bom B
inner join listentry LE ON B.LIST01 = LE.ENTRYID
where list01 is not null;

Post your full SQL

You need to be joining to the listentry table on entryid and retrieving entryvalue to get the text you require.

What versions have you transitioned between?  Webservice engine changed between 9.3.3 and 9.3.4 Also are you sure your new environment was installed with the same paths as your old one as this would make a difference in the URL used to access the webservices.

Use SOAPUI to test your call as Antonio has said either your calling the wrong url or you message is malformed and the method you want to use it not being idnetified from it.

Roles are additive so if your old roles give privilege to edit it, the new role will not override or take away the privilege.

I guess to a large extent they are want you want them to be.  In general we think of parts as physical things represented in PLM that are used to manufacture our products. We include software within parts which while you could reasonably argue are not physical but is required to produce a functional product.  Again for us Documents is where we collect our product design collateral. Beyond the specifications that describe fit form function of the physical parts there are lost of documentation required/produced that are abstracted from articulating the physical item. Here I am referring to thing like product requirements, test plans and reports, simulation output, product architectures. All vital to understanding the evolution of product, but not essential in describing the physical product.

Not a black and white topic, I am sure other swill offer a different opinion.