Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Assessment
Workspace Domino Designer
Created by Guest
Created on Sep 24, 2018

JSON views

We need a 'treat view content as JSON' - this should return valid JSON when opening the view in a browser. Use the view column style to determin the datatype to return.

Domino Data Services is too slow on large views

?ReadViewEntries&OutputFormat=JSON gives a strange format (e.g. returns {"@columnnumber": "8","@name": "$50","number": {
"0": "1854.0258302583"}} when all I need is {"price":1854.03} )

  • Attach files
  • Guest
    Oct 27, 2022

    Was anything done to include built in json views?

  • Admin
    Thomas Hampel
    Oct 27, 2018

    Moving idea to product : Domino Designer

  • Guest
    Sep 25, 2018

    Actually I think it would be better to just add a JSON form type to the NSF.  You can define field names, but the type is probably just 32k text/JSON.  The form type would then be a trigger for view/document rendering. 

  • Guest
    Sep 24, 2018

    This is the very least you must do to support custom JSON.

    Another approach that also support nested JSON objects:

    When rendering our own JSON formats, we treat the Notes view as HTML and set square brackets on the view template. Since Domino does not support custom JSON from views, we are left with a comma too much at the end of the last row. To solve this we add a null value on the view template. Could Domino please remove the last comma, when the view template has the content-type: application/json! Or set the appropriate commas automatically, after each row, except the last.

    Also add the ability to make closing semantics on categorized columns. The formula in a categorized column could be: "{\"category\" : \"" + category_notes_field + "\", \"elements\" : [", but after the last document in the category we need a place to put "],". I imagine a formula field: "Category End" property under "Column Value". That would also be useful for custom XML.