[Index]

API Reference for view/User

Model ref.: view/User

The full URL would include the host-proxy name: https://[host-proxy].

Variables are enclosed in square brackets.

For a list of available UUIDs and their dot notations:
GET /api/v0/data/HierarchyNode/?format=json

Get the Add form

Task Call URL Parameters Response
Get the GUI Add form. GET /api/view/User/add/
  • hierarchy=[hierarchy]
  • format=json
 The GUI Add form of view/User as JSON

The API call to the /add/ URL can only be made from a hierarchy that allows the model type to be added. The actions in the response shows the url for the POST API call to create an instance.

Create

Task Call URL Parameters Payload
Create POST /api/view/User/ hierarchy=[hierarchy]
(For payload specification)

  • Response is a transaction pkid for the create action.

  • The GET call to 
    tool/Transaction/[trans pkid]
    shows the View resource has no instance pkid, because a view model stores no instances.

    • Bulk Export

    Task Call URL Parameters Payload
    Get a selected [export_format] of the schema and instances [pkid1], [pkid2],... of view/User; optionally with tag_version at [version] and Configuration Template as [configtemplate]. POST /api/view/User/export/
    • hierarchy=[hierarchy]
    • version=[version]
    • schema=
    • schema_rules=
    • template_name=[configtemplate]
    • export_format=[raw_xlsx|xlsx|json]
    		 { "hrefs":["/api/view/User/[pkid1]", "/api/view/User/[pkid2]",...]}}

    For export_format=json, the response is a time stamped zip file of data in JSON as in the system database. Item properties such as strings that are empty or Boolean values that are not set, are not included. The filename in the response is of the format as the example:

            Content-Disposition: attachment; filename=export_2013-05-17_14:20:19.186444.json.zip
        Content-Language:en
        Content-Type:application/x-zip

    For export_format=raw_xlsx, the response is a MS Excel spreadsheet with columns corresponding to the JSON format export and a response filename format:

            Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_CCYY-MM-DD_HH-MM-SS.xlsx
        Content-Language:en
        Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

    For export_format=xlsx, the response is a MS Excel spreadsheet, arranged by any Field Display Policies that apply. The columns correspond with those of a Bulk Load Template export sheet. The response filename format is:

            Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_formatted_CCYY-MM-DD_HH-MM-SS.xlsx
        Content-Language:en
        Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

    The XLSX format can be used to bulk load instances of view/User and the JSON format can be used to import instances of view/User.

    • To get the list of all instance pkids [pkid1],[pkid2], ..., use the List GET call for view/User: 
    •  GET http://[host-proxy]/api/view/User/?hierarchy=[hierarchy]

    Export Bulk Load Template

    Task Call URL Parameters Response
    Get a compressed format of the Bulk Load spreadsheet template for view/User POST /api/view/User/export_bulkload_template/
    • hierarchy=[hierarchy]
    • modeltype=view/User
    		 The response is an attachment of the format: filetype_bulkloadsheet.xlsx.gz

    List

    Task Call URL Parameters Response
    List GET /api/view/User/
    • hierarchy=[hierarchy]
    • format=json
    • schema=true
    		 The view/User schema and all instances as JSON.

    (The list will return 0 to 3 view/User instances)

    Help

    Task Call URL Parameters Response
    Get the on-line Help for view/User. GET /api/view/User/help hierarchy=[hierarchy] On-line help of Model ref.: view/User as HTML

    Instance API Reference

    Export

    Task Call URL Parameters Response
    Get a selected [export_format] of the schema and a single instance with [pkid] of view/User; optionally with tag_version at [version] and Configuration Template as [configtemplate]. GET /api/view/User/[pkid]/export/
    • hierarchy=[hierarchy]
    • version=[version]
    • schema=
    • schema_rules=
    • template_name=[configtemplate]
    • export_format=[raw_xlsx|xlsx|json]
    		 The response is an attachment. Refer to the list below.

    For export_format=raw_xlsx, the response is a "raw" MS Excel spreadsheet with columns corresponding to the JSON format export and a response format:

            Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_CCYY-MM-DD_HH-MM-SS.xlsx
        Content-Language:en
        Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

    For export_format=xlsx, the response is a MS Excel spreadsheet, formatted to show all columns and a response format:

            Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_formatted_CCYY-MM-DD_HH-MM-SS.xlsx
        Content-Language:en
        Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

    For export_format=json, the response is a time stamped zip file of data in JSON and a response format:

            Content-Disposition: attachment; filename=export_2013-05-17_14:20:19.186444.json.zip
        Content-Language:en
        Content-Type:application/x-zip

    The XLSX format can be used to bulk load instances of view/User and the JSON format can be used to import instances of view/User.

    For Bulk Export, refer to the Bulk Export section.

    Get

    Task Call URL Parameters Response
    Get GET /api/view/User/[pkid]/ hierarchy=[hierarchy] The view/User instance with [pkid].

    Help

    Task Call URL Parameters Response
    Help GET /api/view/User/[pkid]/help hierarchy=[hierarchy] The on-line Help for view/User.