02 - Building APIs in the Best Order
When building your API, you should think about object dependencies and build the top-level items first.
For example, your application may have the following data types:
Users
Contacts
Practice Areas
Matters (Requires Contacts and Practice Areas)
Time Entries (Requires Matters and Users)
Matter<->Contact Role Associations (Requires Contacts and Matters)
You should prioritize APIs for the items with no dependencies and work toward the items with the most dependencies.
Related Articles
Addendum: Building a Practice Management System
If your organization is building a practice management system, the following guidance will help you build a future-proof application that will not need constant maintenance and refactoring as your client base grows. Database Design Use "long" Primary ...
Push Connector Requirements.
Universal Migrator facilitates migrations between hundreds of different applications into destination applications whom we have built a push connector for. If you are reading this article, you likely want Universal Migrator to load data into your ...
05 - Patterns to Implement & Avoid
When you're building your API, you should avoid falling into the following traps: Patterns to Avoid These are patterns that you should avoid. Avoid Non-JSON Requests/Responses Your API should only accept JSON requests and only respond with JSON ...
Configure PgAdmin 4
Configure PgAdmin 4 In order to backup and restore databases using PgAdmin 4 you must ensure the Binary Path setting points to where several critical DLLs are saved on your hard drive. Below is the path that is typically correct, but it may vary for ...
Universal Migrator Logs
Universal Migrator has three types of logs that you can use to investigate the results of a data extraction or injection. 1. Output Logs Output logs are stored in: %LocalAppData%\Universal Migrator\__Diagnostics\Logs and captures user-visible text ...