Forum Discussion
Select from another table in a live streaming dataset
Per my experience and understanding on streaming dataset, it only supports one table in the streaming dataset by design. You can see that when enabling the "historical data analysis" option for a streaming dataset created via REST API, it converts to a one-table dataset. I think the Dev team might forget to limit the table numbers when creating a streaming dataset via REST API.
So if you'd like to create tiles for the "other tables" in the streaming dataset, just create one streaming dataset with each table.
As to the un-exposed APIs, it is not recommended. I was digging into some un-exposed ones, but it seems we can't pass the authentication. The access token generated from registered app seems not sufficient.
Per my experience and understanding on streaming dataset, it only supports one table in the streaming dataset by design. You can see that when enabling the "historical data analysis" option for a streaming dataset created via REST API, it converts to a one-table dataset. I think the Dev team might forget to limit the table numbers when creating a streaming dataset via REST API.
So if you'd like to create tiles for the "other tables" in the streaming dataset, just create one streaming dataset with each table.
As to the un-exposed APIs, it is not recommended. I was digging into some un-exposed ones, but it seems we can't pass the authentication. The access token generated from registered app seems not sufficient.
Thank you for the reply, Eric! I thought it might be too much of a stretch to try to hack my way into the unexposed API. This makes sense.
