I created the Dashboard and the Dashboard will not allow me to update this with same error. I have other updateable dashboard for the Part Plant so not sure why this one is not working.
Do I need to have all M parts set to Manual first?
ok face palm…I don’t normally add site be since we are adding a new site I included it. I am updating my Training to have all the same Site name. So I will try it then…if not I will remove it from BAQ and just pull from current site.
You might want the BAQ to check the site it (or the dashboard) was launched from. Because I think it might balk if you launch it from site A and then try to update a record belonging to site B. Kind of like how a Packer created in Site B can’t even be looked at from Site `A’
That is what I meant…I just didn’t know the correct terminology. So i will set the BAQ to pull from CurPlant. This way what ever plant they are in it will pull just that info.
I don’t do them enough to really recall all the details of using them properly.
And before you start thinking this is the issue, do a quick check to see if the Plant is in different cases of the tables selected (just include that field from all tables).
First off, I thought there was more than one table, and your uBAQ was retrieving the Plant field value from one table, but then trying to update a different table.
And while “MfgSys” doe equal “Mfgsys” when retrieving the data, updating a record with “Mfgsys” as its value, with a dataset containing “MfgSys”, may fail.
If it is just one table in the BAQ this shouldn’t be an issue at all.
I also have the Part table because I am pulling the Part Description. So I guess they need to be the same too. I wonder if they were different in each part.
I knew that the Plant field was case sensitive now and when importing data i always make sure it is all the same. Odd that when Epicor upgraded our DB during the conversion that they didn’t have it all be the same.
I remember there was a Data Fix we had to get for some folks who had case problems on some fields… especially customers whose data originally came over from Progress (which didn’t care about case) to SQL (which does). I’ve been looking back through various notes but haven’t found anything… I’ll keep looking.