Finance | Project Operations, Human Resources, ...

Invalid Table Name SY01407

(0) Share

Report

Posted on by JBurgess

Upgrading to GP 18.4 I get this error when trying to open the Transaction by Customer Inquiry Window:

I've looked at the DYNAMICS and company tables and SY01407 doesn't exist. It also didn't exist in their previous GP version (GP 2015).

After clicking ok, you can still access the window. Any ideas on to why this is throwing an error?

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (7)

Answers (0)

Joseph Markovich 3,976 on at

Like (0)

Report

Did you have this issue when performing your test upgrades?

This table is new to 18.4 -- where it stores the user defaults for the lookup windows in PM, RM and Bank Reconciliation.

Table, Column and Parameter Changes in Microsoft Dynamics GP October 2021 Release & 2021 Year-End - Microsoft Dynamics GP Community

Since it is new, there isn't any data that was ever stored in it -- I would think support could give you a script to run to create the table and any procedures and fix this.

Joe

Was this reply helpful? Yes No
JBurgess 74 on at

Like (0)

Report

Thanks for the info on this. I didn't run into this during testing, and user testing didn't discover this either. Perhaps MS will put out a fix for this error message to create this table like you suggested. Thanks for reply!

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

If your test databases still exist does this table exist there? If so, use SSMS to create the script to create the table. You could possibly use SQL Maintenance in GP to create this table as well.

Was this reply helpful? Yes No
JBurgess 74 on at

Like (0)

Report

This table was never created in the new version. Not sure why as the 18.4 install went through the upgrade steps with no errors or warnings. I may try to install 18.4 to a test server and script out the table to insert it (assuming it upgrades and creates okay. Thanks for the ideas!

Was this reply helpful? Yes No
Suggested answer

JBurgess 74 on at

Like (0)

Report

Just to follow up on this, I was able to script out the table from an install where the SY01407 created ok (it had no records). I used that to create the table in the DYNAMICS database and the error is no longer there, so I believe this solved the issue.

I still don't know why that table was missed during the upgrade, but for now, this issue is resolved. Thanks for the input!

Was this reply helpful? Yes No
David Musgrave MVP ... 14,095 Most Valuable Professional on at

Like (2)

Report

You should have just been able to use the built in SQL Maintenance to create the table.

Including granting access to DYNGROUP and binding defaults.

David

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

USE [DYNAMICS]
GO

/****** Object: Table [dbo].[SY01407] Script Date: 2/17/2022 9:25:22 PM ******/
SET ANSI_NULLS OFF
GO

SET QUOTED_IDENTIFIER ON
GO

CREATE TABLE [dbo].[SY01407](
[USERID] [char](15) NOT NULL,
[DICTID] [smallint] NOT NULL,
[FORMNAME] [char](79) NOT NULL,
[WINNAME] [char](79) NOT NULL,
[FIELDNAM] [char](31) NOT NULL,
[IntegerValue] [smallint] NOT NULL,
[BinaryValue] [binary](4) NOT NULL,
[DEX_ROW_ID] [int] IDENTITY(1,1) NOT NULL,
CONSTRAINT [PKSY01407] PRIMARY KEY NONCLUSTERED
(
[USERID] ASC,
[DICTID] ASC,
[FORMNAME] ASC,
[WINNAME] ASC,
[FIELDNAM] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
GO

Grant DYNGRP permissons on the table

Was this reply helpful? Yes No