What's New

AutoUpdateService now calls the Manager API (POST /api/updates/check-in) during its hourly update check, sending store vendor type, current version, and update channel. If Manager confirms no update is available, the app never attempts to contact Azure blob storage. When an update is confirmed, only then does the app download the update package details from blob storage. This two-phase approach solves firewall blocking issues some stores experienced when their network blocked direct Azure storage access. If the Manager API is unreachable, the app automatically falls back to the previous direct Velopack check behavior, ensuring update delivery is never blocked by a Manager outage.

Support tickets now include 12 key data points about the user's environment (product version, operating system build, SQL Server edition and version, active database and server names, machine name, store configuration, vendor settings, and POS system type). This comprehensive snapshot enables faster troubleshooting and reduces back-and-forth communication.

The cloud sync proxy client now strips schema prefixes (like "dbo.") from table names before sending requests to the Manager API. Previously, schema-prefixed table names caused HTTP 400 errors because the server's whitelist only contained bare table names. This normalization is applied to all three sync operations: schema retrieval, pending row counts, and batch fetching.

Added automatic normalization of table names in the cloud sync proxy client to strip schema prefixes (like "dbo.") before sending requests to the cloud API. This prevents sync failures that could occur when the local database references tables with schema qualifiers that the cloud API doesn't expect.

The Quick Issue Submit dialog was not including system information (such as vendor ID, store number, POS system, and database details) when submitting support tickets, causing the server to reject submissions with a "Vendor with ID not found" error. The tool now properly collects and sends all required system information including vendor, POS system, database version, and store details.

When submitting a support ticket through the Quick Issue dialog, the system now automatically attaches complete system information including Margin Master version, Windows version, SQL Server details, database name, store number, primary vendor, POS system type, and RSC. Previously, this information was missing from submissions, requiring support staff to manually request it.

Added belt-and-suspenders protection against schema prefix mismatches by normalizing table names on the client side, complementing the server-side fix already deployed in Manager. This ensures sync reliability regardless of which server version stores are running.

The sync proxy now consistently handles both qualified ("dbo.AceCatalogRecords") and unqualified ("AceCatalogRecords") table names across all sync operations including schema retrieval, pending row counts, and batch fetching.

Added PostAndGetAsync<TRequest, TResult> method to IApiClientService and ApiClientService to support strongly-typed POST requests with JSON request bodies and deserialized response objects. This provides a cleaner API for the new Manager update check-in endpoint and future typed POST operations.