Dynasol Contact Scanner Dynamics 365 Business Central Android App

Scan business cards and contacts on Android, synced straight into Business Central.

Dynasol 365 Contact Scanner | Dynamics 365 Business Central Android App
Android App · Dynamics 365 Business Central

Dynasol 365 Contact Scanner

Revolutionize your CRM workflow: scan business cards, sync contact details with Microsoft Dynamics 365 Business Central, and manage leads while you’re on the go.

Scan with OCRCapture key details from business cards
Business Central syncCreate or update contacts through APIs
Android-firstMobile contact access and quick actions
Mobile contact management

Turn business cards into actionable contacts

Dynasol 365 Contact Scanner connects your Android device with Microsoft Dynamics 365 Business Central. Use your phone’s camera to read business-card details, review the extracted information, and send contact data to Business Central through its APIs.

01

For everyday users

Point, scan, and sync. Access your Business Central contact database and use quick actions to call or email contacts.

02

For technical teams

Use the documented integration approach based on OData APIs, OAuth 2.0 authentication, and Azure app registration.

Business card OCRContact syncCall & email actionsOptional local saveOAuth 2.0 / PKCE
Permissions noted in the source: Camera for scanning, Internet for API synchronization, and Contacts for optional local saving. Review the app’s current permission prompts and your organization’s policies before use.
What the app offers

Detailed key features

The app combines contact capture, Business Central integration, and mobile-first actions for sales teams, field representatives, and marketers.

✦

Business card scanning

Use the Android camera and on-device text recognition to extract information from a card.

  • Name, phone, email, and company
  • Address, website, and job title where available
  • Review and edit the extracted details before syncing
↻

Real-time sync with Business Central

Send contact details to Business Central and create or update records. The source describes matching by email or phone to help avoid duplicate contacts.

Offline queueing: the source describes syncing queued work when connectivity returns.

↗

Quick actions: call and email

Open the device’s calling or email workflow from a contact to follow up without manually copying contact details.

▣

Optional local backup

Save selected contact information to the Android address book as an additional local contact copy.

Built for integration

Technical features

Azure authentication

The source describes OAuth 2.0 Authorization Code Flow with PKCE for authentication, with Microsoft Authentication Library (MSAL) for Android.

Performance and synchronization

The source describes delta synchronization and retry/backoff handling for rate-limit responses. Confirm the behavior and limits against the version and API configuration you deploy.

Security-conscious design

The source describes avoiding embedded client secrets in a mobile app and using secure token storage. Follow your organization’s identity, device, and data-handling policies.

Offline data handling

The described architecture uses local caching and background work to support queued synchronization when the device reconnects.

For developers and IT admins

How it works under the hood

The archived product page describes a native Android application that communicates directly with Business Central APIs over HTTPS, without a separate custom backend service.

LayerTechnology described in the sourcePurpose
FrontendNative Android, Kotlin, Jetpack Compose, MVVMMobile interface and application state
API integrationBusiness Central OData APIs over HTTPSRead and write contact data
Local dataRoom / SQLite and WorkManagerLocal caching and background synchronization
Text recognitionGoogle ML Kit Text RecognitionExtract text from business cards on-device
NetworkingVolley and OkHttpNetwork requests to the APIs
AuthenticationMicrosoft Authentication Library (MSAL)Sign-in and token handling
Authentication and configuration

OAuth 2.0 via Microsoft Entra ID

The source’s technical guide outlines an authorization-code flow with PKCE for a public mobile client. Exact settings and permissions depend on your Business Central environment and current Microsoft identity configuration.

01

Check prerequisites

  • An active Business Central tenant (SaaS or a configured on-premises environment).
  • Access to the Microsoft Entra admin center and permission to register applications.
  • A suitable Business Central environment for testing, preferably a sandbox.
02

Register an application

In the Microsoft Entra admin center, open App registrations and create an app registration. The archived page gives “Dynasol Contact Scanner” as an example name and describes a single-tenant registration.

Configure the redirect URI required by the app and its MSAL setup; do not copy a URI without confirming the exact value expected by the app version you use.

03

Record the application identifiers

Keep the Directory (Tenant) ID and Application (Client) ID available for configuration. Treat identifiers as configuration values and store any sensitive credentials securely.

04

Configure Business Central API permissions

The archived page refers to the Dynamics 365 Business Central delegated permission Financials.ReadWrite.All and admin consent. Confirm the correct permission type and least-privilege access for your specific mobile authentication flow and tenant before granting consent.

05

Complete sign-in and token handling

The described flow redirects the user to Microsoft sign-in, receives an authorization code, exchanges it for tokens, and sends API requests with a bearer access token. Use the supported MSAL flow rather than implementing token handling from scratch.

Important: The original page includes implementation-level examples and configuration claims that may be version-dependent. Validate the redirect URI, permission type, scopes, API behavior, rate limits, and token storage against current Microsoft documentation and the app’s actual implementation before deploying.
Business value

Why use Dynasol 365 Contact Scanner?

The product is positioned as a way to reduce manual contact entry and make Business Central contacts more accessible to teams working away from their desks.

BenefitFor end usersFor IT and admins
Less manual entryCapture contact details from a business card instead of typing every field.Use a defined contact-mapping and synchronization workflow.
More current contact dataAccess contact information on the phone and in Business Central.Use API integration to create or update contact records.
Mobile workflowQueue work for synchronization when connectivity is unavailable, as described by the source.Review local caching and synchronization behavior for your deployment.
Quick follow-upStart a call or email directly from a contact.Keep user workflows connected to the device’s native actions.
Identity integrationAuthenticate through the configured Microsoft sign-in flow.Manage app registration and permissions through Microsoft Entra ID.
Optional local copySave selected contacts to the Android address book.Set policies for device permissions and local contact data.
Product information

App details

App nameDynasol 365 Contact Scanner
PlatformAndroid
IntegrationDynamics 365 Business Central
Version listed in source1.0.0.4
Release date listedOctober 30, 2025
DeveloperDynasol Technologies LLC

Version and release details reflect the archived page and may not represent the latest app-store listing.

Dynasol Technologies

Bring contact capture closer to your Business Central workflow

Explore the Contact Scanner app and review the identity and API configuration required for your environment.

USA: (+1) 302 487 8820   ·   Pakistan: (+92) 423 713 8365
Email: info@dynasol.tech