Simple Object Designer Documentation
Index

Common Issues

This page covers frequently encountered problems in Simple Object Designer and their solutions.

First Things to Try

A large share of reported problems are resolved by one of these four steps. Try them before digging deeper:

  1. Update SOD to the latest version from AppSource, and publish again — updating alone changes nothing until you republish.
  2. Refresh Symbols with cache clearing — SOD Setup page > Refresh Symbols > answer Yes to clear the cache.
  3. Test in an Incognito / private browser window — the Business Central client caches aggressively.
  4. Clear page personalization for the affected page.

Also confirm you are always working from the same company. SOD customizations apply to all companies in the environment, but SOD itself should always be operated from one company; switching companies causes symbol and cache errors.

Startup and Access Issues

SOD Won't Start / Session Locks Up

Symptoms: SOD gets most of the way through downloading symbols, then the page disappears and never starts. Afterwards no other screens can be launched — the whole session is locked. It repeats on every attempt, possibly across all environments.

Cause: a known Business Central bug affecting the SOD main menu. A saved bookmark or menu link pointing at the old main menu page will not open.

Resolution:

  1. Update Simple Object Designer to the latest version in the Admin Center
  2. Launch SOD via Alt+Q (Tell Me / Search), not from a saved bookmark
  3. Stop using the old bookmark — a new menu page exists, and old bookmarks point at the one that will not open

SOD Not Found in a Company

Symptoms: The SOD page cannot be found in one company, or does not appear in Alt+Q search or bookmarks, although it opens correctly by direct URL.

Facts:

  • SOD customizations apply to all companies in the environment. There is nothing to set up per company.
  • The Alt+Q search result is not provided per company by SOD — the behaviour is identical behind the scenes everywhere.
  • The SOD page number is 70310321. It can be opened directly with the &page=70310321 URL parameter and bookmarked, even when it is missing from search.

Solutions:

  1. Suspect permissions first — to operate SOD, the user must be SUPER with a blank company specified
  2. If the page opens by direct URL but is missing from search in one company, that is a Business Central inconsistency, not an SOD limitation. Restart the environment from the Admin Center; the condition has also been observed to clear on its own afterwards.

SOD Appears Read-Only

Symptoms: The designer looks view-only; changes cannot be made.

Facts: this is not a trial or free-version restriction. SOD has no read-only mode.

Checks:

  1. The user has a proper Business Central license (Premium or Essential)
  2. The user has the SUPER permission set
  3. If license and permissions are correct, it is usually a client-side caching problem — refreshing or clearing the browser cache has resolved it

A symptom that often precedes this is symbol downloads taking a very long time or appearing to hang. If it persists after clearing the cache, capture screenshots of the read-only screen and contact support@hougaard.com.

Cannot Get Back Into the Environment

Symptoms: a customization — commonly a Role Center change — has left you unable to open pages or navigate.

Recovery: jump straight to the My Settings page by appending ?page=9204 to the environment URL:

https://businesscentral.dynamics.com/[tenant]/[environment]/?page=9204

From My Settings, switch to a profile you have permissions for.

Symbol Download Issues

Cannot Download Symbols

Symptoms: Download fails, no symbols available

Solutions:

  1. Verify permissions (SUPER or Snapshot Debugging)
  2. Check internet connectivity
  3. Clear browser cache and retry
  4. See Symbol Troubleshooting

If the download fails specifically with No published package matches the provided arguments, this is a known Microsoft bug. Update to the latest SOD version, which contains a workaround. See Symbol Troubleshooting and Updating SOD.

Symbols Outdated

Symptoms: Missing tables/pages, new objects not showing

Solutions:

  1. Re-download symbols
  2. Typically needed after BC updates
  3. Or after installing new extensions

Publishing Issues

Publish Fails

Symptoms: Error during publish, deployment fails

Common causes and solutions:

Cause Solution
Compilation error Fix code issues (check error message)
Schema conflict May need Force Sync mode
Permission issue Verify deployment permissions
BC service issue Wait and retry
Allow HttpClient Requests disabled Turn it on for SOD in Extension Management
Incomplete query or untyped feature field Complete or delete the object
API endpoint on an obsoleted table Remove the endpoint

Allow HttpClient Requests deserves a specific mention: if publishing works in one environment but fails in another — typically fine in production, failing in a sandbox — check this toggle for the Simple Object Designer extension in Extension Management. It is not reliably carried over when a sandbox is copied from production.

For the full error-by-error index, see Publishing Failures.

Publish Fails on an Obsoleted Table

Symptoms: Publish fails with an error that a source table "is obsoleted", and SOD closes.

Cause: an API endpoint exists on a table that has been obsoleted or removed in the current BC version.

Solution: remove the API endpoint referencing that table, then publish again.

Refreshing Symbols Doesn't Fix It

Symptoms: the same compilation error persists after refreshing symbols and updating every installed app.

Likely cause: a placement or calculated field references an anchor field name that does not exist on the target page.

Fix: correct the anchor to an existing field. Use Get Source Code from selected error to locate the reference.

Changes Not Appearing

Symptoms: Published but changes not visible

Solutions:

  1. Verify deployment completed
  2. Clear browser cache, or test in an Incognito window
  3. Clear page personalization for the page
  4. Refresh the page
  5. Check deployment status

A successful publish only deploys what SOD is configured to produce. It does not restore functionality that came from a different app. If a publish succeeds but an expected value is still missing, first establish whether that data ever came from SOD at all — see Columns disappeared after an upgrade.

Field Issues

Field Not Showing on Page

Symptoms: Created field, placed it, but not visible

Check:

  1. Is placement configured correctly?
  2. Is anchor valid?
  3. Is field marked as hidden?
  4. Is extension published?
  5. Browser cache — open the page in an Incognito / private window
  6. Page personalization — stale personalization can prevent a newly added field from displaying; clear personalization for that page

Microsoft's client caches aggressively, which is why a new field can appear for one user and not another. If none of these resolve it, send the generated .app file to support — rename it to .txt so it passes e-mail filters.

Field Visible to Some Users but Not Others

Symptoms: A custom field is visible to some users and not others, with no obvious pattern — sometimes present one day and gone the next.

Cause: the users are missing the permission set from the SOD-generated app. Custom fields created by SOD require that permission set.

Resolution: assign the app's permission set to the affected users.

Do not use SUPER as the fix. If the field only appears when a user has SUPER, that is the diagnostic — it confirms the app's permission set is missing from their normal permission configuration. Having access to tables and pages from earlier SOD customizations is not sufficient either; each app's permission set must be explicitly assigned.

Useful diagnostics: confirm whether the affected users have identical permissions, and whether the behaviour reproduces in an InPrivate/Incognito session (to rule out browser cache).

Newly Created Field Not Offered for a Page

Symptoms: a field you just created does not appear in "Add existing fields to pages and reports".

Cause: that task lists only fields that already exist. Newly created custom fields are not placed from there.

Solution: place it via the Placed on pages column on the Add Fields page — click the Not Placed value and choose where the field should appear. This applies to every field type, including Option fields intended as drop-downs.

Field in Wrong Position

Symptoms: Field appears in unexpected location

Solutions:

  1. Review anchor selection
  2. Check AddBefore vs AddAfter
  3. Verify anchor exists
  4. Adjust placement index

Group Not Showing on Page

Symptoms: a group added to a page does not render.

Cause: the group contains no fields. An empty group does not display.

Solution: add at least one field to the group.

Posting Fails After Adding a Custom Field

Symptoms: posting a document fails after adding a custom field and configuring field transfers to related tables.

Cause: the Field Numbers for "the same" logical field are not aligned across the related tables — a Business Central quirk.

Solution: add the Field No. column to the New Fields list via personalization, give the same logical field the same Field No. on every related table, then publish. Full procedure in Field Transfers.

"The type between two fields must be the same"

Symptoms: an error claiming two fields must have the same type, where the fields are unrelated and the types genuinely differ between a source table and a transfer target.

Cause: field numbers are out of sync between the two tables.

Solution: add the Field No. column via personalization, correct the number on the target table so the two match, and publish. See Field Transfers.

Errors Inserting Records with Configuration Packages

Symptoms: inserting new records — for example through Configuration Packages / RapidStart — into a table with SOD-created fields fails, while updating existing records with the same fields succeeds.

Cause: Business Central performs an automatic field transfer when it detects the same field number in certain cases. If two custom fields in different tables share a Field No. but have different data types, that automatic transfer conflicts and errors.

Principle: fields that should transfer must share a field number; fields that should not transfer must not share one.

Steps:

  1. Open Create new fields in SOD
  2. Use personalization to add the Field No. column
  3. Look for two fields in different tables with the same Field No. but different data types
  4. Give one of them a different, unused Field No.
  5. Publish

Inserting a single field first, or recreating fields on a related table, does not address the underlying collision.

FlowField Decimal Places Ignored

Symptoms: a FlowField with Decimal Places set (for example 0:0) always shows 2 decimals on the page, and changing the setting between 0 and 6 makes no difference.

Cause: a defect in SOD versions before 12.0.0.552.

Solution: update SOD to 12.0.0.552 or later. See Updating SOD.

FlowField on an Option Field Reports "Must Not Be Blank"

Symptoms: displaying an Option field from another table through a FlowField errors that the field must not be blank, although the source Option field is correctly configured with valid values.

Cause: a defect in SOD's handling of FlowFields that reference Option fields.

Solution: update SOD to the latest version, where this is fixed.

Page Crashes After Switching Language

Symptoms: a page containing a FlowField crashes when opened after changing the Business Central display language — for example the Item Card crashing when switching between Norwegian and English.

Cause: the FlowField filter uses a date formula written in one language ([t-2å..] or [t-2y..]). Date formulas are language-dependent unless made explicit.

Solution: wrap the formula in angle brackets so it is always interpreted as English: use <-2Y..>.

Columns Disappeared After a BC Upgrade

Symptoms: columns that used to be there are gone after a Business Central upgrade — which can be triggered by events such as a license expiring and being renewed.

Facts:

  • An upgrade can force-uninstall extensions that are not compatible with the new BC version.
  • Vanished columns are not necessarily SOD's. They may have come from an unrelated third-party app.
  • Specifically, the Customer Name and Vendor Name columns on General Ledger Entries and related pages/reports are commonly provided by a separate app called "G/L Source Names" — this is not part of Simple Object Designer. That app can become incompatible with newer BC versions and be removed during a force upgrade.

Guidance: when standard-looking name columns disappear after an upgrade, check whether a separate app was providing them, and check with your BC partner. Re-creating such a column as a plain SOD field produces a blank column — a new field holds no data unless a lookup or transfer fills it. See Field Transfers.

Financial Reports (or Another Feature) Breaks After Adding Fields

Symptoms: after creating custom fields on certain tables, a Business Central feature such as Financial Reports stops working — the page or report appears broken or empty.

Diagnostic: removing the SOD customization from that table makes the feature work again.

Cause: extending specific base tables that a feature depends on — the Financial Reports table is a confirmed example — breaks that feature.

Resolution: when a BC feature breaks after adding fields, check whether you extended the table it depends on. Remove or revise that table's customization and republish. If the cause is not obvious, send the generated .app file to support@hougaard.com.

Unexpected Field Number Requirements

Symptoms: field number validation demands an unexpectedly high starting number when creating a new table or feature.

Cause: a known bug in an earlier SOD version.

Solution: update SOD to the latest version.

Feature Issues

Feature Not Verified

Symptoms: Feature shows "Not Verified"

Solutions:

  1. Check for duplicate names
  2. Verify field configurations
  3. Review required fields
  4. Fix any validation errors

"An invalid argument was passed to a 'List' data type method"

Symptoms: publishing a feature fails with this message. The AL call stack references Build Feature Code Hgd → ExportTableFields / ExportTable.

Cause: one or more feature fields have no Type selected. In the Feature Fields list an unset Type shows as 0.

Fix: open the Feature Fields list, find every field whose Type shows 0, and assign a valid type. Every field must have a type before publishing.

"The Anchor Table does not exist"

Symptoms: opening any feature produces The Anchor Table does not exist. Identification fields and values: Table No.='<number>' — even for features unrelated to that table number.

Solution: update SOD to the latest AppSource version via Admin Center / Extension Management, then reopen the features. See Symbol Troubleshooting.

Setup Field Not Appearing on the Setup Page

Symptoms: a primary key or other field on a setup-style feature does not appear on the setup page, even though the field is placed in a group, the feature verifies with no issues, the extension was republished several times, and deployment status is Completed.

Cause: the field's grouping in the "Setup" feature is misconfigured.

Resolution:

  1. Go to Tasks > Create new features
  2. Open the feature named Setup
  3. Check whether your feature's field is present there
  4. Confirm it is marked to be shown on the card page
  5. Correct the grouping if the field is missing or not marked to display

This can affect one feature while others created the same way work fine — it is a per-feature configuration issue, not a global publishing or symbol problem.

Auto Primary Key / Number Series Not Generating

Symptoms: the automatic primary key stopped assigning values on a feature.

Checks, in order:

  1. A number series is linked to the feature
  2. The number series line is valid and not exhausted (Last No. Used vs Ending No.)
  3. Default Nos. is enabled
  4. Use Number Series is still on in the Feature Card
  5. The number series is linked in the SOD Setup for the current company — open it via Alt+Q and search for "<Object Prefix> Customizations Setup"
  6. Republish the feature

If the configuration looks right and the problem persists after a BC major update (BC 28, for example), re-download symbols and republish.

Cannot Delete a Feature Table — Dependency Error

Symptoms: deleting a feature table or its setup errors with something like "Table <TableName> is depended on this table, cannot be deleted", often with a page error prompting a refresh (F5).

Cause: another table — typically a related or list table — has a dependency on the one you are deleting.

Solution: resolve the dependency from the dependent table first. Removing feature tables that have dependencies or data may require Force Sync — see Force Mode.

Note: if you are trying to delete the table because auto-numbering is broken, do not. Assign a number series to the primary key via the app's Setup page instead.

Role Center Part Captions Not Displayed

Symptoms: custom captions entered for Role Center Parts do not appear — the parts show a generic caption such as "Activities" instead. This affected any part regardless of language, and deleting/recreating the role center or changing display language did not help.

Cause: a defect in SOD, fixed in 12.0.0.568.

Role Center Part Added After Publish Doesn't Appear

Symptoms: a Role Center Part added after the RoleCenter feature was already published does not show, and the tool does not detect the change.

Cause: a defect in SOD, fixed in 12.0.0.568. Update SOD.

Role Center Menu / Action Group Changes Not Appearing

Symptoms: a group or action added to a Role Center does not appear after publishing.

Guidance: Role Center navigation actions must be added through the RoleCenter feature template's page actions (Embedding, Creation, Processing, Reporting) — not via New Sections, Page Groups, or field placement.

Limitation: the Navigation action group is not supported on Role Centers in the current version.

Compound Mandatory Field Condition Rejected

Symptoms: a compound mandatory-field condition is rejected, with the target field shown in red.

Solution: update to the latest SOD version first — a recent bug affected this behaviour. Then check the setup against the "Conditional Business Logic" section in Advanced Rules.

"Something went wrong" When Saving a Filtered View

Symptoms: saving a filtered view on a list page fails with "something went wrong". Filtering itself works; only saving the view fails. It can affect a single user while others on the same page are fine.

This is not a permission problem. It occurs even for users with SUPER and with the feature in their permission set.

Root cause: a known Microsoft Business Central bug, confirmed on BC 26.1 (Platform 26.0.35091.0 + Application 26.1.33404.35168).

Resolution: clear the user's personalizations on the affected list page. The offending personalization can exist even if the user never knowingly personalized that page.

Steps that do not help (so you do not waste time): adding the feature to the permission set, verifying SUPER, checking the browser version.

API Issues

API Not Accessible

Symptoms: Can't reach API endpoint

Check:

  1. Is API configured correctly?
  2. Is extension published?
  3. Are credentials valid?
  4. Is entity name correct?

API Returns No Data

Symptoms: API works but returns empty

Solutions:

  1. Verify data exists in table
  2. Check field selection includes data
  3. Review any filters
  4. Test with known data

API Not Returning the Newest / All Rows

Symptoms: the consumer shows older records but not the most recent ones, while the current rows are clearly visible in the Business Central table view.

Checks:

  1. Confirm the data is present and current in the BC table view
  2. Refresh the query or dataset in the consuming tool to rule out a stale cache — note that refreshing will not bring back records beyond the BC limit
  3. If the table holds more than roughly 20,000 records, the Business Central per-call record limit is the likely cause: the API returns a truncated set, and newer rows may not be in it
  4. Create a fresh report or connection and re-fetch, to rule out a broken consumer connection

Cause: Business Central's ~20,000 record limit on API calls. SOD adds no filtering or limitation of its own.

Document-Table Endpoints Return Errors

Symptoms: Item and Vendor APIs work, but Sales Header, Sales Line, Sales Invoice, Sales Invoice Line and similar document tables return errors when the OData feed is opened.

Cause: the primary key of these document tables includes the Option/Enum field Document Type along with other composite key fields. Every key field must be exposed for the entity key to resolve.

Solution: verify that all primary key fields of the source table — including Option/Enum key fields such as Document Type — are included in the API field selection. Inspect the generated API page source to confirm, then republish.

Deployment or Update Fails Because of a FlowField in an API

Symptoms: an error appears while updating Business Central that references a FlowField, although you do not believe any FlowField is enabled in SOD.

Cause: one or more FlowFields are included in a table API created under Expose Data > Expose data as web service APIs. The FlowField comes from the source table's own fields, not from a field you created.

Resolution:

  1. Open the API Endpoints list
  2. Open the API for the affected table (e.g. the Item API)
  3. Find the included FlowField(s) in the field list
  4. Uncheck them
  5. Republish

Concrete example: on an Item API, Coupled to Dataverse and Service Commitment Option are FlowFields that need removing.

FlowField in a Query-Based API

Symptoms: an error when consuming a query-based API — in Excel, for example — after adding a new field.

Check: whether the new field is a FlowField. FlowFields are not supported in queries and will cause the API to error.

Solution: remove the FlowField from the query, or use a regular table API endpoint instead, which does support FlowFields.

API Publish Fails After a BC Update (Removed Standard Field)

Symptoms: the environment cannot be updated; publishing fails even after disabling the field elsewhere.

Cause: an API endpoint includes a standard field that Microsoft removed in the new BC version.

Solution: open the affected endpoint's field list, set the removed field(s) to not Included, and republish before performing the environment upgrade. See Business Central Updates and Create API Endpoints.

Publishing an API Fails with AL0161

Symptoms: publishing an API for a standard table fails with AL0161 ... inaccessible due to its protection level.

Cause: the table is restricted by Microsoft and contains protected fields — table 8889 "Sent Emails" is a known example.

Resolution: the table cannot be exposed via API. This is a Microsoft limitation with no SOD workaround; choose a different table or approach.

A Previously Working Endpoint Returns 400 Bad Request

Symptoms: an endpoint that worked now returns 400 Bad Request from a client such as Excel.

Guidance: deleting, recreating and republishing the endpoint is not the fix. APIs do not deteriorate over time — a recurring need to recreate one indicates a malformed request rather than a corrupt endpoint.

Checks:

  1. Inspect the request URL for encoded control characters such as %09 in the object prefix or entity set segment
  2. Confirm the object prefix and entity set name match the SOD configuration exactly
  3. Reproduce the request from a different client to isolate client vs. endpoint

Record Creation Fails After the BC v27 Upgrade

Symptoms: an API POST (create) that previously worked starts failing after upgrading to BC v27, while PATCH (update) still works. Typical error: Internal_RecordNotFound: The No. Series does not exist.

Cause: BC v27 introduced a completely new number series implementation at the platform level. This is not an API or SOD problem.

Known trigger: if a number series has a "last issued number" out of sync with the starting number, BC v27 can assign blank numbers, which makes record creation fail.

Resolution: review the number series setup for the table the API writes to. This is platform behaviour, not something configurable in SOD, and correcting it usually involves a BC partner. Note that assigning manual number series codes through the API — building a code from a prefix plus a customer number, say — does not exempt records from the changed validation.

Internal_RecordNotFound on Business Logic Calls

Symptoms: a business logic API POST returns Internal_RecordNotFound, typically where the invoked method removes the record it was called against (registering or posting style operations).

Checks: confirm the target record exists at call time, and that the bound action is not being called twice.

If the operation genuinely succeeds but the error is returned every time: update SOD to 12.0.0.560 or later and republish.

"New elements must be added at the end of the query"

Cause / current limitation: queries with more than 2 tables (data items) are currently unreliable. This is a known product limitation, not a configuration mistake.

New data items are appended at the end of the elements list, but adding a third or further table may still produce this error even when the element is at the end. Improvement to multi-table query support is in active development. Until then, expect queries over two tables to be unpredictable.

Performance Issues

SOD Running Slowly

Symptoms: Pages load slowly, operations lag

Solutions:

  1. Large symbol caches may be slow
  2. Consider environment performance
  3. Reduce complexity if possible
  4. Report persistent issues

Publish Takes Too Long

Symptoms: Publishing seems stuck

Check:

  1. Large extensions take longer
  2. Check deployment status
  3. Environment may be busy
  4. Wait before retrying

On BC27 the publishing screen may appear frozen because of a Microsoft bug — but publishing usually completes anyway. Check Extension Management to see whether the app version incremented. See Publishing Failures.

Error Messages

"Object Already Exists"

Cause: Object ID conflict

Solutions:

  1. Choose different Start Object Number
  2. Check for overlapping ranges
  3. Review other extensions' ID ranges

"Field Not Found"

Cause: Referenced field doesn't exist

Solutions:

  1. Re-download symbols
  2. Verify field name spelling
  3. Check table reference

"Circular Dependency"

Cause: Objects reference each other

Solutions:

  1. Enable Dual-App mode
  2. Restructure if possible

"Permission Denied"

Cause: Insufficient permissions

Solutions:

  1. Verify user permissions
  2. Check SUPER assignment
  3. See Permissions Matrix

"Unexpected Compiler Output"

Cause: an issue during compilation / .app creation — not with your field configuration.

Solutions:

  1. Refresh Symbols with cache clearing, then retry
  2. Switch back to the Legacy Compiler on the SOD Setup page and retry
  3. Update SOD to the latest version via BC Admin Center (select environment > Apps > update)

See Publishing Failures.

"using RegisterTableConnection or New-NAVTableConnection"

Cause: a CRM, CDS or Dataverse table — identified by "CRM", "CDS" or "DataVerse" in the name — is referenced somewhere in the extension. This has nothing to do with whether you use CRM interactively.

Solutions:

  1. Search the whole extension for objects referencing such a table
  2. Include API endpoints in the search (Expose Data > Expose data as web service APIs) — an exposed CRM/CDS/Dataverse table triggers this even when the feature you are editing does not use it
  3. Remove the offending table, field, page or endpoint and republish

"The Field MetaData ... does not exist"

Cause: a FlowField filter references a field number that does not exist on the target or related table. It has also been observed specifically after upgrading to BC v28, where the same configuration published fine on earlier versions.

Solutions:

  1. Locate the FlowField — it may live on a standard table such as Vendor — and correct the filter's field number
  2. If the filter value cannot be edited in SOD, delete the field, publish with Force Sync, then re-create the field with the correct filter and publish again
  3. Also check for Lookup fields pointing at tables or fields that no longer exist

"The record in table Field MetaData Hgd already exists"

Cause: a symbol refresh running against a cache that was not cleared.

Solution: decline the refresh prompt when opening SOD, then run Setup > Refresh Symbols and answer Yes when asked to clear the cache.

"AL0132: 'Record ...' does not contain a definition for '<field>'"

Cause: a field was deleted in SOD but is still referenced by a generated API page or page extension, and/or the symbol cache still holds the removed field.

Solutions:

  1. Uninstall the app
  2. Open SOD > Setup page > Refresh Symbols, answering Yes to clear the cache
  3. Publish again

Remove the field from all page placements, report placements and API endpoints as well — see Create New Fields.

"AL0185" / "PTE0004" permission set errors

Cause: a generated query or table has no matching entry in the extension's permission set. Seen when publishing a new query that links to custom/feature tables, or when publishing features.

Resolution: send the generated .app file to support@hougaard.com for analysis. Rename it to .txt if the mail is blocked.

"The filter ... is not valid for the FieldName field on the Field MetaData Hgd table"

Symptom: creating a field transfer, or exporting the extension, using a source field whose name contains parentheses — "Outstanding Amount (LCY)", field 92, for example — fails with an error ending Did not expect '('. The call stack references Modern Build Extension Hgd (codeunit 70310262).

Cause: a confirmed SOD defect in handling field names containing parentheses.

Resolution: update SOD to the latest version. Parentheses in field names are not an unsupported limitation — this was a bug and it is fixed.

"Sorry, we just updated this page. Reopen it, and try again."

Symptom: setting a default on a list page (for example the Financial Reports API List page) returns this message, and reopening the page does not clear it.

Cause: when reopening does not help, it is not a transient condition — it can be a bug in the installed app version.

Solution: install the latest app update from AppSource, then retry. See Updating SOD.

"The supplied field number 'NN' cannot be found in the '...' table"

Symptom: importing a SOD configuration into another environment fails with this message, often naming the API Pages table.

Recommended resolution: avoid importing SOD configuration between environments. Keep SOD in a single dev sandbox and deploy elsewhere with the .app file only — see Environments.

If it must be diagnosed, send the error's Copy Details to support@hougaard.com.

"Extension is not compatible with this Business Central version"

Symptom: after installing BC updates, the SOD-generated extension shows as incompatible, even though the latest SOD update is installed.

Cause: the generated extension references a Microsoft field that was removed, or moved to a different app, in the new BC version.

Solution: open the compatibility/deployment email produced by the upgrade to see which field is at fault, remove that field's use in SOD, complete the BC upgrade, then re-create the usage against the field's new location. See Business Central Updates.

Recovery Steps

If Things Go Wrong

  1. Don't panic - Most issues are recoverable
  2. Note the error - Screenshot or copy message
  3. Check status - Deployment status, extension status
  4. Research - Check this documentation
  5. Seek help - Support forum if needed

Getting Support

To have support inspect a generated extension, send the .app file to support@hougaard.com. Rename the file to .txt before sending, otherwise e-mail attachment filters will block it. For compilation and package validation errors, use Download Source and send the resulting ZIP instead.

Rollback Options

If customizations cause problems:

  1. Modify in SOD and republish
  2. Uninstall extension via Extension Management
  3. Restore from backup (.app file) — see Environments

Preventive Measures

Test First

  • Always test in sandbox
  • Verify before production
  • Keep .app file backups

Document Changes

  • Track what you change
  • Note why changes made
  • Keep version history

Stay Updated

  • Keep SOD updated, and republish after updating
  • Re-download symbols periodically
  • Update SOD before a Business Central major version update
  • Review release notes