At FTC we are starting to experiment with the REST API and I was wondering if anyone been able to call a View successfully from the REST DataService?
I have been running into issues with this as the Dataservice responds that it can't find the "table" (read:view).
The help doc seems to suggest views are supported, and I'd really like to start making some for various user-specific dashboards/single-purpose workstations
http://www.tessituranetwork.com/Help_System/Content/System_Tables/TR_DATA_SERVICE_TABLE.htm
As of last November my understanding was that support for views through DataService was not yet enabled. That's about all I know about it though--hopefully somebody will be able to illuminate a little bit further, as I'm interested to know, too.
We will be adding support for Views, although not sure at this point whether it will be in v12.0 or in v12.5
Thanks for the update, Chuck!
Hi
I get
"Description": "Table 'LV_SC_APIS_EVENT_ARTIFAX_MATCH' was not found in schema 'dbo'.",
And I can see the view under the dbo schema
The v12.5 documentation says "The TR_DATA_SERVICE_TABLES table (added v11) is used to register custom tables and views as resources for the DataService service of the REST API."
Can anyone confirm or deny :) whether views should be acccessible in v12.5 ?
Thanks
Aryaguna
The service does not support views. This is likely a bug in the documentation.
-Sam
Hi Sam,
A documentation bug perhaps, but also a REST API bug? I'm confident that 99.999% of all custom data that people are going to want to expose via the REST API will be views.
--Gawain
[duplicate]
Hi Gawain, thanks for the update! I will let the team know.
Thanks Gawain, Samuel
I think a read-only views custom data feature would be extremely helpful to folks.
Having read-write is fraught with difficuties to make into a general case, but what about something like, this?
Specified in a separate table
TR_DATASERVICE_VIEWS
without the next_id... and probably regeistered_with... and subentites columns
I'd think that could be based around the exisiting code for TABLES fairly easily and be a great feature
But thanks for clarifying that it's not ready just yet :)