On Prem API Ability
J
Jake
We would LOVE the ability to access an API that is tied directly into our database and not something where we need to upload to the could. We have some internal systems where if I were able to obtain project information (status, cost, etc), I could automate many aspects of what we do. We would love for the API to be current when a user checks in a project and not have the additional step of uploading to an integration.
B
Biagio LaRosa
Eduardo Voloch Any progress here on a true API capability on prem? Just watched the V18 release video and no sign of any API enhancements at all.
Eduardo Voloch
Biagio LaRosa: Here are the API enhancements on V18
• Automatic Purchase Order Export
• Endpoint to allow metric units on data import
• Tags endpoint on GET Products Catalog
• Description endpoint on the POST Service Orders
• Tasks Export Automation from Gantt View
• IntegrationProjectId null on GET Projects call
• Add missing change order fields for rejected date and change order name
A decision has not been made in regards to an on-premises API.
T
Tim Ogilvy
Finally found the closest feature they have, it's not under workflow settings, it's under Project settings.
In both Si13 and 14.
Still only seems to push to "the default integration" which seems like a problem... I'm not even sure how D-Tools decides which integration is default.
Also not sure why it's not a part of workflow rules.
Eduardo Voloch
Tim Ogilvy: Default integration: Select a project and click on “Export” to integration. There, click on the checkbox. This will “add” the integration to the “Default”. This was intended to skip a few steps when automatically exporting a project. As our API utilization has grown, we definitely need a better way, such as the ability to remove an integration from the default integration. To view the active default integration, go to the Project History and note the details of the auto-project export. We will improve that on our next release.
T
Tim Ogilvy
Eduardo Voloch: Thanks Eduardo, always appreciate your hard work!
Hoping to have some time to chat again soon about the API, there's a few really cool things I'd like to be able to do with it, but I'd like to understand your plans and design patterns before I get too excited about suggestions! 🤓
Eduardo Voloch
Tim Ogilvy: Absolutely! Thank you Tim. Please send me an email when you have a moment so we can coordinate a call. eduardov@d-tools.com - Thank you sir!
T
Tim Ogilvy
This also applies to those of us who are running our own cloud based implementation of D-Tools on AWS or Azure etc.
The current D-Tools API is far from real-time, and requires many complex manual steps to update, and it seems to be evolving further and further away from any sensible REST or equivalent API standards.
The one positive thing D-Tools have done recently in this space, is allow the project settings to automatically push projects to the cloud on Check-in, but this still pushes to D-Tools' cloud servers in the US which breaches sovereignty compliance requirements for us, and for many other companies under GDPR or other legislation with data sovereignty requirements.