Project and Portfolio Management Practitioners Forum
cancel

Field (-4837) does not map to a Section (null)

SOLVED
Go to solution
Highlighted
Alan Delimon
Super Contributor.

Field (-4837) does not map to a Section (null)

When trying to pull up one of our request types in our 7.5 instance, we get the following error:
Field (-4837) does not map to a Section (null)

I tried to open this in the workbench to debug and get the same error there.

This request was created in a 6.0 instance and migrated with the upgrade from 6.0->7.1->7.5. It has not been modified in 7.1 or 7.5.

A screenshot of the error is attached.
5 REPLIES
Katy Cabral
Respected Contributor.
Solution

Re: Field (-4837) does not map to a Section (null)

Hi Alan,

we just experienced this a few weeks ago after migrating several request types. The problem was in the request type header, and the support area had to create a script for us to run that would update our DB tables on the back-end.


--Katy
Darshan Bavisi
Outstanding Contributor.

Re: Field (-4837) does not map to a Section (null)

Hi Alan,

It seems HP created this defect in 7.x version (mostly 7.5), as many people are experiencing this issue. So yours is not an isolated issue. HP already has a defect id created for this to resolve in future upgrades.

This primarily happens due to mismatch in the KNTA_SECTION_LAYOUTS table, where the details of the fields in which section on the form belongs to is stored. In our case also, HP created a few scripts to identify the exact issue area that resolved the issue. I would say log a service request with HP and they should resolve it quickly, as they are getting this request from multiple customers and know the issue areas.
PPM Guru
Regular Contributor.

Re: Field (-4837) does not map to a Section (null)

As the previous poster said. Create a support ticket and let HP deal with it. We noticed in our 7.1 --> 7.5 upgrade that there was issues with how the new table component section fields where converted from the old table component format. We decided to side-step the conversion risk by changing the request layout for the table component fields in 7.1 before we ran the 7.5 upgrade script. We had less issues after we did that. Not sure if this is related to yoru problem or not.
Alan Delimon
Super Contributor.

Re: Field (-4837) does not map to a Section (null)

They appear to be dealing with it for us now. I'm curious to see the resolution.
Magic_Wand
Contributor.

Re: Field (-4837) does not map to a Section (null)

Alan,

There is no generic way to resolve this error. But usually there are data missing in table knta_section_layouts. We need to manually insert the data. The missing data usually belongs to the request header type. Some customers reported this issue before, but none of them are able to reproduce it.

We have seen this with 7.1 SP7 and SP9 after migrating from a lower version.

Resolution is to call PPM support and have someone give you a script to insert the data.
================================
SELECT * FROM users WHERE clue > 0