|
|||
|
|||
I am really sorry, but I have to insist. We need to insert about two thousand contracts and we'd strongly prefer to do it automatically. It is a bulk operation that we have to do only once.
So, I have two more questions for you about our problem: 1) Can we insert Contracts just once directly via db? If we cannot, could you please further explain what is the problem in doing it via db INSERT statements? 2) If we can do those INSERT commands via db (just once), can you show us how to generate some correct REC_IDs for the new Contracts? Thanks a lot, Fabrizio |
|
|||
|
|||
Thank you for asking again. Unfortunately the answer is still no :( The API supports many different entities of RangerMSP (Accounts/Items/Charges/Appointments/Tasks/Tickets/Quotes/Etc...) however not Contracts and you should never ever perform any direct database operation. This will end up breaking the integrity of the system and might cause numerous issues.
In case the Contracts repeat themselves then in RangerMSP you can create one Contract with all details and then use the Copy option to copy it to other Accounts, this should be a time saver. Hope this helps. |
|
|||
|
|||
Thank you for posting this.
The Web API supports adding many different entity types, however, it does not support adding Contracts at this time. We may be able to offer you an unofficial access to a low level API that will support adding Contracts, however we need to learn more about your requirement. We recommend that you email us (support @ ) the complete list of fields you intend to pass when creating the new contract, the exact type of contract you want to create. We will review the information and will back to you with the update. Hope this helps. |
|
|||
|
|||
Let me ALSO request this.
Not ONLY this, but I'd request that CommitCRM move to delivering API first, or "as-a-first-class-citizen" development approach: https://nordicapis.com/sessions/deli...class-citizen/ We shouldn't have to "ASK" for access to functions in the application, it should be our choice on how to get something done, either in the API, UI, import, or webUI... but really you should be able to do everything with the API. Also, don't mean to pile-on, but it desperately needs to be a modern RESTful WEB API. this is 2020 after all, and the current API is not fun to work with at all... |
|
|||
|
|||
If the CommitCRM API is replaced with something more modern, consider gRPC.
Google designed gRPC and then open sourced it. Microsoft are on board. https://docs.microsoft.com/en-us/asp...aspnetcore-3.1 As is Netflix, Dropbox etc https://medium.com/@sankar.p/how-grp...t-30408bf42794 https://www.cncf.io/netflix-case-study/ https://code.tutsplus.com/tutorials/...pis--cms-30711 https://www.yonego.com/nl/why-milliseconds-matter/#gref |