Failure: Title was not found on the data object error while configuring the list form

[ganesh-sanap]

Category

• Bug

Describe the bug

While configuring the list form using "Configure layout" option, getting below error on New form:

Failure: Title was not found on the data object.

This is happening only when "debugMode": true. This error disappears once I start entering value in Title field.

Steps to reproduce

1. Go to SharePoint online list form and select "Configure layout".
2. Select "Header" inside "Apply formatting to" drop-down.
3. Copy JSON from Configure custom header & paste in the JSON text input area.
4. Click Save.
5. Open New form and you will see the error at top.

Expected behavior

It should not show an error message, instead it should show blank in place of [$Title].

• Can this be handled by default on new form?

Environment details (development & target environment)

• Your Developer Environment: Windows 10
• Target Environment: SharePoint Online
• Browser(s): Chrome

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[bcameron1231]

The error is happening because you are customizing an empty form. When you select New, and then customize the layout there is no data context.

As per the instructions on the documentation, open an existing item.

If you still think this is something you'd want changed, I would probably go to the UserVoice and add a suggestion. In my opinion, it is not a bug.

[ganesh-sanap]

@bcameron1231 It doesn't matter from where I am customizing the form (new/display form). The issue is with "debugMode": true. Whenever I am adding this in JSON, saving it and opening new form it is showing below error:

But display/edit form works fine.

I think we should not use "debugMode": true in final JSON while saving.

Question: Is it possible to avoid this error on new form while using "debugMode": true in JSON?

IMO, we should remove "debugMode": true from documentation examples as this error might be confusing to users (like here).

[kkowal89]

If you turn the "debugMode" to false, he will accept the null value inside the new form, cause the value is not yet initialized. So What I did for example was this:

{
"debugMode": false,
"elmType": "div",
"attributes": {
"class": "ms-borderColor-neutralTertiary"
},
"style": {
"width": "100%",
"border-top-width": "0px",
"border-bottom-width": "1px",
"border-left-width": "0px",
"border-right-width": "0px",
"border-style": "solid",
"margin-bottom": "16px"
},
"children": [
{
"elmType": "div",
"style": {
"display": "flex",
"box-sizing": "border-box",
"align-items": "center"
},
"children": [
{
"elmType": "div",
"attributes": {
"iconName": "FileRequest",
"class": "ms-fontSize-42 ms-fontWeight-regular ms-fontColor-themePrimary",
"title": "Details"
},
"style": {
"flex": "none",
"padding": "0px",
"padding-left": "0px",
"height": "36px"
}
}
]
},
{
"elmType": "div",
"attributes": {
"class": "ms-fontColor-neutralSecondary ms-fontWeight-bold ms-fontSize-24"
},
"style": {
"box-sizing": "border-box",
"width": "100%",
"text-align": "left",
"padding": "21px 12px",
"overflow": "hidden"
},
"children": [
{
"elmType": "div",
"txtContent": "=if([$Status]=='','New document request',if([$Status]=='Created','Created document request',if([$Status]=='Rejected','Rejected document request','Requested document')))"
}
]
}
]
}

This lead to the effect you want to have, but only in "debugMode":false, otherwise SharePoint will be picky!

[Gennady-G]

This is happening only when "debugMode": true.

Thank You @ganesh-sanap for clarification.

Best regards, Gennady

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.