Fix trip detection Azure Functions

• Update to latest nuget version of Azure Function SDK
• Target functions version ~1 in one click deployment

v1.2.3

Release 1.2.3

Fixed a deployment issue in the earlier version.

v1.2.2

Release 1.2.2

Fixed a bug that happened when trying to add a previously deleted device.

v1.2.1

Release 1.2.1 (Mobile client only)

This release is mainly targeted towards the mobile client. We've added the ability for the mobile client to detect if the location services is disabled at the start of trip recording and prompt the user to enable it.

v1.2.0

Release 1.2.0

This is a large release containing new features, many bug fixes, and some changes that are backwards incompatible.

If you have built a service integrating with your BMFT deployment, please read the API breaking changes section.

New Features

1. Circular Geofences (APIs + Portal)

   • You can now define geofences from a point and a radius in meters, in addition to the existing geofences from polygons.

2. Webhooks for geofences (APIs + Portal)

   • Added the ability to recieve webhook notifications, in addition to the existing email notifications, when geofences are triggered.

3. Asset locations in other tabs (Portal)

   • You can now see the current locations of your assets which viewing the geofences, dispatching and locations tabs

4. API Swagger Documentation

   • Updated to Swagger 2.0
   • Added documentation for all controllers
   • Controllers return documented DTO objects

5. iOS Client Support

6. Batch creating resources (APIs)

   • You can now batch create most resources. Useful if you are integrating your BMFT deployment with another service.

7. Tagging resources and searching by tag/name (APIs)

   • Another feature tailored towards integrating with other services
   • Useful for organizing resources (assets, devices, etc...) when you have a large number of them

Other changes

1. Changed Ids of Assets, Locations and Geofences to strings

   • To ease integration with other services, the Ids of the core resources has been changed to strings, which may be defined in the post call or autogenerated if left out.

2. Command line build support for backend

3. Delete button for assets and devices in portal

4. Upgraded to .netstandard2.0 across all projects in the backend

5. Added missing delete action to locaitons controller (thanks Manojattal)

6. Add support for AAD V1 as an authentication provider

API Breaking Changes

1. Asset.Name is a newly introduced required field.
   • It has been back-filled with Asset.Id
2. Geofence.Id has been changed from int -> string
   • Existing Ids retain their values
3. Location.Id has been changed from int -> string
   • Existing Ids retain their values
4. User.Id has been changed from guid -> string
   • Existing Ids retain their values

v1.1

Performance fixes:

• Compile Automapper mappings
• Geofence intersections checks in DB
• Minor SQL query optmiziations
• Update instead of append GeofenceUpdates

Bug Fixes:

• Fix bug where Geofence geometry was inverted if user specified geofence points right-handedly

Initial Release

The Bing Maps team is pleased to announce the availability of our complete asset tracking solution for small fleets. The solution was previewed in September 2017 at Microsoft Ignite in Orlando and is now available for download and customization. The Bing Maps Fleet Tracker solution includes the Azure based back end of services and storage, a web interface for tracking assets, and client code for Android phones.