S
Stefan Antonitsch
Hello! Is there a current timetable for when the API connection will be implemented? Thank you guys
Arne Semmler
The “SQL dump” item has now been moved to a separate Canny point: https://projo.canny.io/feature-requests/p/api-call-sql-dump
This point is renamed to API call accordingly.
Arne Semmler
planned long
Arne Semmler
planned
Benedikt Voigt
Our current vision is that we will offer both in the long term:
1) daily backup (an SQL dump just for yourself as a company, not to be reimported into projo)
2) API interface
R
Ruben Hauser
Benedikt Voigt: API would be extremely important and useful for the future.
Arne Semmler
under review
J
Johannes Hanf
I would also prefer an API interface with a view to the future. The days of backing up and copying SQL databases are actually over or are no longer easy to do if you use AZURE services in the cloud instead of having physical servers in the office. Even with a database export, a lot of documentation is required in order to be able to assign the data in a meaningful way. In the case of an interface, this can be built up successively and supplemented by areas.
So clearly from my side 2).
Arne Semmler
Johannes Hanf: Hi Johannes, your objection is completely correct and is shared by us. However, we can actually provide a database dump faster than an API. And I assume that the dump can also be a useful option for purposes other than connecting BI services. We can also store the dump in suitably protected cloud storage, so that this is not a manual download, but a snapshot that is stored at a point that has yet to be defined.
We have/create the documentation of these structures for our own developers anyway, so that it can also be made available to external developers. It is clear that the dump is a first step for us and will be followed by an API. However, both are functions that are not intended for normal users, but rather for developers anyway. Either way, the documentation won't be end-user documentation.
Benedikt Voigt
planned
C
Christopher Yelegen
Hi Benedikt,
For starters, solution number 1 would be completely sufficient, as I don't want to write anything to the databases via an interface. The 24h delay is not that bad.
For me, the only question is: How many views and in which format are they exported? It is not just about project data, but about ALL data (personnel, invoices, customers,...)
Thanks in advance!
Benedikt Voigt
Christopher Yelegen: hello Christopher, in solution number 1) we would provide you with the complete SQL database with your data. Only the uploaded documents would not be included, but all other raw data (personnel, time, invoices, customers,...).
We want to briefly discuss this at UserGroup tomorrow morning (on June 2nd at around 9:45).
Maybe you'll join in?
Meeting ID: 832 3356 7764
Code: projo
Benedikt Voigt
I could think of two possible solutions here
1) We provide you with a backup copy every day, which you can download and integrate into your business intelligence solution.
This would give you access to the complete raw data, but only with a 24-hour delay. In addition, the database can change continuously.
2) We are gradually building API interfaces. These must be versioned and well documented.
At the same time, it will never be as flexible as 1).
What is preferred?
S
Schleimer, Niklas
Benedikt Voigt: Hi Benedikt, please implement variant 2.
reasons:
- API is a worldwide standard for exactly such cases. Actually, that's enough reason;)
- always up-to-date data. The backups are always out of date (e.g. - ad hoc planning not possible due to illness)
- no administration and no cumbersome handling of the backup copy
- Unwanted local memory usage
- no SQL knowledge required
- no additional tools required
- no huge download volumes (or upload to you). In contrast to the backup solution, only what is needed is requested.
- therefore no performance losses in projo
R
Ruben Hauser
Benedikt Voigt: +1 for variant 2!
Load More
→