@gmichaud ccUsing the network inspector, I found that we’re sending a POST request to:https://connection.host/frameset/workspaceWith ASP.NET session cookies and CompanyID cookie, and a JSON body like this:{title: "WorkspaceName", icon: "iconName", areaID: ""}I think I am going to give it a try, but would be nice to have it documented somewhere ;)
One additional consideration that I’d like to point out in favour of exposing two endpoints, one purely for GI ODATA, and another one for the current generic DAC-based endpoint:The necessity to provide a “godlike” user role (OData v4 User) for the DAC-based endpoint. Which the customers are scared of, for security reasons. With the GI-based endpoint, they like the fact that they can set up screen-based access rights to GI screens without invoking row-level security. Off-topic: as we discussed with Andrew Boulanov on the Summit, this issue can potentially be tackled by introducing a special security mechanism just for that endpoint, where general access could be forbidden, but various user roles can be assigned access to different “query hashes” or “query prefixes” (filters and selects need to be allowed dynamic for obvious reasons) Much more importantly, the weight of the metadata. Sometimes just accessing the current “generic” OData v4 metadata file times out our requests on a cold s
We don’t use Atom/XML or JSON Verbose. So, if you roll out the v3 compatibility layer without those two, works for us :) Flipping GI ODATA endpoint to ODATA v4 syntax completely is fine with us, too. We actually already “migrate” your result sets to v4 internally after receiving the data. Please make sure the time-zones are respected in the input/output! We had a lot of struggle with that previously; special thanks to Vladimir Panchenko who ensured consistent UTC results sets in the current dataset. Overall, as long as ODATA is still supported in GIs, we’re fine with either option (compatibility layer or switching v4, or even both if you can expose them in two separate endpoints)To be clear, having the GI-based ODATA endpoint available is very important to us, we just don’t care too much about the protocol version :)
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.