You’re offline. This is a read only version of the page.
580
Hi,
We are upgrading GP from version 16.00.0814 to 18.2.1100 with mostly standard modules (Cnd Payroll, Human Ressources, PSTL). When upgrading Dynamics DB, all goes well. When we try to upgrade the companies we get the following error:
The following SQL statement produced an error:
exec seeSVCOpenRMACountsDetail_Create 2 exec seeSVCRTVCountsDetail_Create 2 exec seeSVCServiceCallCountsDetail_Create 2
ERROR [Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name 'SVC Return Type'.
The following SQL statement produced an error:
exec seeSVCOpenRMACountsDetail_Create 2 exec seeSVCRTVCountsDetail_Create 2 exec seeSVCServiceCallCountsDetail_Create 2
ERROR [Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name 'Service Record Type'.
This happens for all companies including TWO. I've looked around and found nothing. Any idea what could be causing this issue?
**Note: If I do re-add sample data on TWO, it works and I can log in GP in TWO.
Hi, to generate the new scripts, once you have recreated the TWO company;
1. Go to SQL, navigate to the list of views in TWO.
2. For each views that needs to be recreated in the production company, right click on the view and click generate new Create script.
3.Now go to the production company, delete the old views and recreate them using the scripts you have generated.
Hi, what are the scripts??
Hi Derek,
Thank you very much for your help. It helped me solve the issue.
Note that also had 'RTV Status' column, the GP views that had this column:
HistoryRTVLines
HistoryRTVs
RTVLines
RTVs
Here is what I did:
1. In GP 2016, I re-add sample data company on TWO
2. Using SQL, I script all the views listed above from the TWO company
3. I deleted all views listed above from the company
4. I recreated the views in the company database using the script generated in SQL
5. I open the GP 18.2 utilities and did the upgrade on the company database
So, these columns showing as 'invalid column name' are not table columns, as they have spaces in the name, which the columns/fields in Dynamics GP tables won't have, but Views will have.
In the company database, searching for the 'Service Record Type' column, the following GP Views will have this column:
FieldServiceCalls
HistoryFieldServiceCalls
HistoryRMALines
HistoryRMAs
RMALines
RMAs
WorkOrders
For the 'SVC Return Type' column, the GP Views that have this column are:
ContractLines
Contracts
HistoryContractLines
HistoryContracts
HistoryRMALines
HistoryRMAs
RMALines
RMAs
I wasn't able to find any cases where we've seen an upgrade of Dynamics GP fail on these 'invalid column name' errors either, though it looks like the scripts are looking for these columns in the GP Views and not finding them.
The columns appears to be related to Field Services, so, if Field Services is not used at all in the company databases, you may have the option to re-initialize Field Services anew at the new version, instead of attempting to upgrade this feature, which is a core feature, installed with Dynamics GP whether it is used or not.
Let us know if you have any questions.
Thank you,
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (