We are investigating a project for a customer where we need to navigate to selected files in BIM 360 Docs and have encountered a few issues with the API. Some more urgent than others. The aim of the project is to select a subset of documents and deliver them in to a target system. The Main issues we have encountered so far are:
Prio 1:
1. We are unable to seach/find/ select objects based on their custom metadata
This is a major issue since the customer want's to
1. Use Metadata to identify the documents that are marked for delivery
2. Transfer the metadata with the delivery so that they do not have multiple sorces of information, and so that they do not have to enter the data manually again in the target system(s)
Another issue is here with the 360 DOCs UI itself, they need to be able to inherit/reuse the Custom Metadata settings over several folders/Projects. Today it is impossible to secure that the same preferences are used over the entire system and it is a very tedious work redoing all of the metadata for every folder. (possibly 100ds to 1000nds)
Prio 2:
2. Why do we get different Data for different objects? (Even Team and Docs have different results when doing the same queries)
For Docs:
- Search, searches and returns Version, here the DisplayName == The fileName (Description not available)
- FolderContents, returns item, here the DisplayName == Description?!? (FileName not available, if description changed we do not have a chance to present anything useful in a custom browser)
The problem here is that we can't create a proper browser without multiple queries which will make it extreemly slow
Can we do a search that returns just the item, or a folder query that returns the version so that i do not have to do special treatment for one of them?
We do get a lot of data with the queries, just not the data we need (Filename, all Attributes etc)
Great to have:
3. Folder parents
- We need a way to get the folderstructure upwards in a single query to show the "full path" now we need send multiple requests to accomplish this
The reason for all of this is because we can't modify the existing browser or add functionality to the Viewer in the Docs UI, so we need to have ourv own browser.
___
Ability to iFrame the 3legged login to be able to use Sharepoint Online as a Collective place for Online services our users.
regards
Håkan Wikemar, AEC AB, haw@aec.se
