Can AD Data Connector API calls impact other currently executing APIs?
The existing projects will remain in 360 and only new projects will utilize ACC.
Here is our potential scenario:
ACC will be using the DC API approach
360 API pipeline continues in tandem with ACC API based on amount of work to transition dashboard/reports
Does anyone have any experience or information?
Will this cause resource issues like throttling, data locking, etc. OR are they actually two different data capture streams and will Not impact each other?
Searched on AD but didn't see any specific information.
Related
I tried to translate a big IFC file (150mb) for the veiwer and it took around 15 minutes only the translation without the uploading part. So is such translation time normal and can it be done something about it? I am currently using the free credits only for testing. Is there a performance increase with the paid credits?
The /modelderivative/v2/regions/eu/designdata/job is used with the advanced conversionMethod:modern.
No, there is no performance difference between trial and paid accounts. Forge dev account with a valid trial plan can use full Forge features as paid one as I know.
What happened after submitting a translation job?
After submitting a translation request and it returns success, it means that your translation request is sent to our service and has been put into the translation queue successfully. It doesn't mean that your model will be processed by our service immediately.
Instead, you have to line up! Since our service resources are limited and shared worldwide, you will need to wait for enqueued IFC translation jobs from other Forge users completed, and then our service will start to process yours. Therefore, waiting for 15mins is not slow from my perspective.
I'm trying to obtain a full list of my project issues using the method described in the following document:
Issues - GET Issues
Quality issues
The list I get doesn't match the one available in the BIM360 portal. Quality issues are not common project issues.
Can you provide some examples or the set of methods available to get that information?
We found this thread is related to the Classic Field after having a live meeting today. To get issues from Classic Field, we need to use Classic Field API (link) instead, not the Forge BIM360 Issues API. Forge BIM360 Issues API can access issues data of the BIM360 Field Management and Document Management only currently. They are totally different systems. 😊
I can't see Usage Analytics after using Derivative api.
I see only current credit balance on Autodesk account page, but I need informations about consumption of my apps separately.
Only for first Billing period it's shown detail data correctly (other two months are empty).
Unfortunately as of now our usage analytics still can’t break usage data down by apps yet - will let our Engineering know it’s good to have the breakdown available and update this answer when it’s there.
I am currently in the process of implementing pagination, sort and search functionalities in the project files/plans/sheets views of BIM 360 Docs integration.
Since I couldn't find any best practices regarding to these features, I thought I would reach out so that I don't keep stuck reinventing the wheel.
Background:
Most of the implementation uses https://github.com/Autodesk-Forge/forge-api-dotnet-client/ SDK.
Based on what I saw it looks like there is no built-in results sorting in the Forge/BIM 360 APIs. BIM 360 Docs looks as if it sorted results on the client.
One has to cache all the results as structured data on the client in order to provide the sorting functionality. That also does not play well with any pagination approach.
Question:
Is there a way to sort results using the API, so that they come back in a predefined order, also while paginating?
According to our engineering team, the "sort" feature isn't currently supported by Forge Data Management API. Apologizing for the inconvenience caused.
I have logged a request FDM-1813[Support sorting in APIs of BIM360 integration] in our internal system to our engineering team to allocate time to evaluate the possibility. As it required some time to complete this task, please remember this request id for the future reference. You're welcome to track updates or provide additional information by quoting this request id via forge.help#autodesk.com.
However, a workaround is to fetch all data from the API, then sorting on the client side via Javascript.
Cheers,
I have Windows Service that accesses Outlook items through Exchange Web Service (EWS). It often experiences concurrency issues.
Based on this doc, a maximum of 27 connections per user can be made concurrently for Exchange Online. I couldn't find documentation for the detailed throttling policies for Microsoft Graph.
Is there anyone know if I can make more concurrent connections in Graph API than EWS? Also, does Graph API show better performance in general than EWS such as response time?
This is documented in Microsoft Graph throttling guidance. There is also an in-depth look at Throttling patterns available.
Each endpoint throttles a little differently. For Exchange/Outlook endpoints it is 10,000 requests per app id, per user, within a 10 minute window.
The term "connections" doesn't really apply to an API like Microsoft Graph. As a REST-based API, it is fundamentally stateless. Each request is a self-contained transaction.