I can see tables and data by running SQL queries. How do you prevent system for SQL Injection? Also I would like to know how it can help customer to get most out of it.  I asked "Give me 10 asset inspections recently created." it was giving Fault code data.

SQL Ingection for Geotab Ace Feature

I would like to update DVIR Defect to resolved but I can't find official document which show which method and what will be the body.

Does anyone know how to find official CRUD Operations provide by Geotab to update data via API?

I would like to replicate the same environment as our production setup in order to thoroughly test upcoming features and ensure integration stability with Geotab. This includes access to the same types of data (e.g., DVIRs, defects, device activity, diagnostic logs), configurations, and permissions that exist in our live environment. The goal is to validate changes in a controlled and accurate environment before pushing them to production, minimizing risks and ensuring consistent behavior across both environments.Please let me know what options are available to replicate our production configuration — such as test databases, sandbox environments, or data mirroring — and any recommended approach from your side.

I would like to replicate the same MyGeotab environment as production for testing purpose.

page-user page-user-vaibhav-mavani-2063 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

I can see tables and data by running SQL queries. How do you prevent system for SQL Injection? Also I would like to know how it can help customer to get most out of it.  I asked "Give me 10 asset inspections recently created." it was giving Fault code data.

I would like to update DVIR Defect to resolved but I can't find official document which show which method and what will be the body.

I would like to replicate the same environment as our production setup in order to thoroughly test upcoming features and ensure integration stability with Geotab. This includes access to the same types of data (e.g., DVIRs, defects, device activity, diagnostic logs), configurations, and permissions that exist in our live environment. The goal is to validate changes in a controlled and accurate environment before pushing them to production, minimizing risks and ensuring consistent behavior across both environments.Please let me know what options are available to replicate our production configuration — such as test databases, sandbox environments, or data mirroring — and any recommended approach from your side.

Nesenās aktivitātes

SQL Ingection for Geotab Ace Feature

Does anyone know how to find official CRUD Operations provide by Geotab to update data via API?

I would like to replicate the same MyGeotab environment as production for testing purpose.