After installing R2 .725 on top of .661 I was running utilities then an error popped up -- thoughts?
*This post is locked for comments
After installing R2 .725 on top of .661 I was running utilities then an error popped up -- thoughts?
*This post is locked for comments
to the posters wondering what this table is and if it is important to the users it holds data about the command bar.
DictID | ResType | ResID | TechnicalName | PhysicalName | Sequence | FieldID | FieldName | PhysicalName2 | DataType | ControlType | Length | Keyable |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 1 | 7937 | ListDictID | ListDictID | ID_INT | Integer | 2 | 4 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 2 | 7938 | ListID | ListID | ID_INT | Integer | 2 | 4 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 3 | 7939 | ViewID | ViewID | LI_MasterNumber | Long Integer | 4 | 9 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 4 | 7727 | CmdParentDictID | CmdParentDictID | ID_INT | Integer | 2 | 4 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 5 | 7728 | CmdParentFormID | CmdParentFormID | INT5_RU0 | Integer | 2 | 5 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 6 | 7726 | CmdParentCmdID | CmdParentCmdID | INT5_RU0 | Integer | 2 | 5 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 7 | 7729 | CmdSequence | CmdSequence | INT5_RU0 | Integer | 2 | 5 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 8 | 7719 | CmdDictID | CmdDictID | ID_INT | Integer | 2 | 4 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 9 | 7720 | CmdFormID | CmdFormID | INT5_RU0 | Integer | 2 | 5 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 10 | 7721 | CmdID | CmdID | INT5_RU0 | Integer | 2 | 5 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 11 | 4594 | Priority | Priority | INT5 | Integer | 2 | 4 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 12 | 7998 | ButtonSize | ButtonSize | INT5 | Integer | 2 | 4 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 13 | 7715 | CmdCaption | CmdCaption | STR79 | String | 80 | 79 |
0 | 1 | 1237 | syListViewCmdBar | SY07240 | 14 | 7736 | Visible | Visible | CB_Visible | Boolean | 2 | 0 |
Hello everyone!
I do see most of everyone that has posted is having issues with the error in regards to the SY07240 table.
"Cannot insert the value NULL into column 'CmdSequence', table 'DYNAMICS.dbo.SY07240'; column does not allow nulls. INSERT fails.*/"
I was sent an email today which directs to the a Known upgrade issue blog.
[View:~/gp/b/dynamicsgp/archive/2015/06/10/draft-known-upgrade-issues-when-upgrading-to-microsoft-dynamics-gp-2015-r2:550:50]
As a few people have mentioned Development is working hard at getting these issues resolved. It appears that we have a workaround for this issue however, a support incident would need to be entered in which when it is closed it will be set as non-chargeable.
If you have any questions please let me know!
~Thomas Newcomb
------------------------------------------
Microsoft Dynamics GP Support
------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights
Tim,
BTW, awesome work on the fix, thanks for sharing!
We recently faced a similar upgrade situation... we went GP 2010 SP3 to GP2013 SP2 to GP 2015 RTM. I wonder if this is how we dodged this particular bullet?
We are having the same issue with the SY07240 table. As others are mentioning, the script is looking for (CmdParentFormID = 1576). That CmdParentFormID is not in the table nor is a reference to that CmdParentFormID or FormId of any kind in any supporting table.
We could probably come up with a clever workaround for now; however, the logic tells us that we may just need this new form and related command to actually work.
Hopefully a hotfix resolution is available soon.
I heard from Terry Healy that the development team is hard at work to get a fix together for us!
I had this exact same issue when upgrading from 11.00.2248 (GP 2010 SP4) to 14.00.0725 (GP 2015 R2). Just like Tim mentioned, the insert statement it was dying on was using a subquery to get max+1 on a sequence number, but no records existed for the where clause, which gives us the NULL and obviously inserting a NULL value into any column in a GP table will fail since all columns are defined with NOT NULL. I inserted a copy of the records in SY07240 I had in a test GP environment that had just Fabrikam in it, and the upgrade completed without any issues. Like you mention, Tim, I'm not entirely sure what this table is used for beyond what its description is, which is "List View Action Pane" (perhaps something to do with Navigation Lists). In any case, I'm definitely not proposing this as a solution, but I can confirm that the upgrade is expecting data in this table that's not there. I'm not too concerned with moving forward with my solution for my specific purpose since this is just a test upgrade, but I'll be keeping tabs on this thread to see if someone from Microsoft responds with a detailed technical explanation or if Michael Sampson responds after he hears from Terry Heley. In any case, the good news is that many of us are running into this so we're all in the same boat.
Harry,
I was going from GP2010 SP2 -> GP2010 SP5 -> GP2015 RTM -> Patch (x3) -> GP2015 R2
I had no issues until GP 2015 R2. I suppose it could be a result of the "hops" version to version (me skipping 2013)
It looks like the GP team assumed there would be certain records populated in the table.
SET @Count = 0
SELECT @Count=COUNT(1)
from SY07240
WHERE ListDictID=0 and ListID=300 and ViewID=2 AND CmdParentDictID = 0 AND CmdParentFormID = 1576 AND CmdID = 41
If I run the SQL above against my SY07240 in my production GP 2010 environment I get 0 records returned.
The next statement (Without my ISNULL stuff)
if @Count = 0
INSERT INTO SY07240 (ListDictID , ListID , ViewID , CmdParentDictID, CmdParentFormID,
CmdParentCmdID, CmdSequence, CmdDictID, CmdFormID,
CmdID, Priority, ButtonSize, CmdCaption, Visible)
SELECT 0, 300, 2, 0, 1576, 38,
(SELECT max(CmdSequence) from SY07240
WHERE ListDictID=0 and ListID=300 and ViewID=2 AND CmdParentDictID = 0
AND CmdParentFormID = 1576)+1 as NewSequence,
0, 1576, 41, 0, 0, '',1
The query in the above select returns <NULL> and <NULL>+1 still is <NULL>
Boom!
I imagine I should go to my Production environment (prior to Upgrade) and follow your good advice and DELETE the records in SY07240 and let GP rebuild. My issue is: I don't know a lot about this table and worry that I may be deleting something one of my users needs or cares about.
Tim
does it have to do with a combination of install package to upgrade path?
I just heard from Terry Healy - the Microsoft team is looking into this. Only some people are experiencing this....
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,280 Super User 2024 Season 2
Martin Dráb 230,214 Most Valuable Professional
nmaenpaa 101,156