Forum Discussion
Calculated Field Not Displaying in Form Custom Header
Carl_Williams I have tested this from my end and I am able to reproduce this issue. I think this is a bug while using calculated column in JSON form formatting.
The calculated column value is available in the page context but it is not shown in form header:
I have raised a new bug/issue here: JSON Form formatting: Unable to use the calculated column value in header/footer layout customization. Hopefully Microsoft will fix this in near future.
Similar thread: Get value of Name column from SPO list for JSON formatting in the header
As a workaround for now, you can try replicating same logic you used in calculated formula using JSON formatting in header layout.
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.
For SharePoint/Power Platform blogs, visit: Ganesh Sanap Blogs
Carl_Williams I have tested this from my end and I am able to reproduce this issue. I think this is a bug while using calculated column in JSON form formatting.
The calculated column value is available in the page context but it is not shown in form header:
I have raised a new bug/issue here: JSON Form formatting: Unable to use the calculated column value in header/footer layout customization. Hopefully Microsoft will fix this in near future.
Similar thread: Get value of Name column from SPO list for JSON formatting in the header
As a workaround for now, you can try replicating same logic you used in calculated formula using JSON formatting in header layout.
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.
For SharePoint/Power Platform blogs, visit: Ganesh Sanap Blogs
- Thanks ganeshanap! HOWEVER, been down this road way too many times in the past. I won't hold my breath on any microsoft alleged 'triage' of fixing anything. It'll probably fester for a couple of years where people will likely be forced to do, wait for it...............................hacks and workarounds.
We'll see though.
Thanks again.
