PartUOM Table in 9.05.702

No, They consolidated it, if on the UOM table if it is not set to part specific it will not store the info in this table any more, it will pull the UOM's from the Unit master. This has created a headache here too for me since I relied on this table




________________________________
From: Bill Jackson <fujijapman@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Monday, August 26, 2013 2:56 PM
Subject: [Vantage] PartUOM Table in 9.05.702



Â
Am I going crazy, or is the PartUOM table empty in 9.05.702?

We just wnet live with 9.05.702, I first noticed when our SQL replication table 'PartUOM' appeared empty..
I wrote a quick BAQ for the table, empty..

Yet in Part Tracker, the EpiBinding for the EpiGrid is still 'PartUOM'. ?

[Non-text portions of this message have been removed]




[Non-text portions of this message have been removed]
Am I going crazy, or is the PartUOM table empty in 9.05.702?

We just wnet live with 9.05.702, I first noticed when our SQL replication table 'PartUOM' appeared empty..
I wrote a quick BAQ for the table, empty..

Yet in Part Tracker, the EpiBinding for the EpiGrid is still 'PartUOM'. ?


[Non-text portions of this message have been removed]
From: Bill Jackson <fujijapman@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Monday, August 26, 2013 3:56 PM
Subject: PartUOM Table in 9.05.702



Am I going crazy, or is the PartUOM table empty in 9.05.702?

We just wnet live with 9.05.702, I first noticed when our SQL replication table 'PartUOM' appeared empty..
I wrote a quick BAQ for the table, empty..

Yet in Part Tracker, the EpiBinding for the EpiGrid is still 'PartUOM'. ?

[Non-text portions of this message have been removed]