microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

C/FRONT functions not working properly and throwing exceptions while connecting database of Business central on premise v14

Open
#517 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

We are currently using NAV 2009 R2. We are upgrading our NAV to Business Central on-premises v14. We are getting errors while using below functions with Business Central on-premises v14 development environment and due to the errors our extensions are not working.

DBL_SetNavisionPath
DBL_LoadLicenseFile
DBL_ConnectServerAndOpenDatabase
DBL_Allow
DBL_OpenTable
DBL_SetFilter
DBL_FindRec
DBL_NextRec
DBL_CloseCompany
DBL_CloseDatabase
DBL_Exit

Please refer the attached screen shot for the error we are getting. It will be good if we have a screen share session so that we can better explain our code and scenario.
Error

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the listed C/FRONT functions and the attached error screenshot, then reproduce the failures against Business Central on-premises v14. Compare the behavior with the stated NAV 2009 R2 setup and identify which functions fail and under what conditions. Done means the compatibility issue is isolated and a supported correction or limitation is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
database
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.