• Replies 17 replies
  • Subscribers 0 subscribers
  • Views 77 views
  • Users 0 members are here
Options
3sides - Social sharing widget
Related

Display iSheet Data on Home Page/Wiki

Sean Pillai
27343

I recall that there is a simple way to display iSheet records on a site's home page (or wiki) in a table or single-item format.  I'm referring to data from each individual row as opposed to charts and other aggregate data visualizations.  However, I haven't been able to find the instructions.  Any assistance would be appreciated.  I'm trying to display iSheet data in a more user-friendly manner by, for example, placing the contents of each column in a separate row, with each iSheet row corresponding to a separate table on the home page/wiki.

 

Simplified example:

(1)  This is my iSheet record:

 

Client Name Client Jurisdiction Client Code Client Mailing Address Client Relationship Manager(s)
Acme Co. Delaware 1234567 123 5th Ave., New York, New York Bob Smith; Amy Jones

 

(2)  I'd like to generate the following on the home page/wiki (including a link at the bottom that would allow the user to edit that particular record):

 

Client Name Acme Co.
Client Jurisdiction Delaware
Client Code 1234567
Client Mailing Address 123 5th Ave., New York, New York
Client Relationship Manager Bob Smith; Amy Jones

Edit Record [THIS LINK WOULD TRIGGER AN EDIT OF THE RECORD

 

]]>
Parents

  • Wondering if HighQ implements a feature where they provide a JS api hosted on the domain where it just re-uses the logged in session details to authenticate rest api calls from the front end, would it be better long term by simplifying usage for custom apps run on the domain front end. If the user logged in, they already proved they are a valid user, I feel like the rest api (if used from the front end) should leverage this and not need to re-authenticate with a token again. Tokens should be more for authenticating from external apps.

    If we compare with SharePoint platform, this is doable in both the on prem and online version. With on prem, it just works for GET and you can pass in a digest token (already available on the page) for POST. For online, you can use PnPjs and pass in a context object (also available with the page) to make rest calls. Super simple and no need to worry about oAuth tokens, though that is available too if you want to connect from external apps.

Reply

  • Wondering if HighQ implements a feature where they provide a JS api hosted on the domain where it just re-uses the logged in session details to authenticate rest api calls from the front end, would it be better long term by simplifying usage for custom apps run on the domain front end. If the user logged in, they already proved they are a valid user, I feel like the rest api (if used from the front end) should leverage this and not need to re-authenticate with a token again. Tokens should be more for authenticating from external apps.

    If we compare with SharePoint platform, this is doable in both the on prem and online version. With on prem, it just works for GET and you can pass in a digest token (already available on the page) for POST. For online, you can use PnPjs and pass in a context object (also available with the page) to make rest calls. Super simple and no need to worry about oAuth tokens, though that is available too if you want to connect from external apps.

Children
No Data