web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / The tax component code...
Small and medium business | Business Central, N...
Suggested Answer

The tax component code is unavailable

(2) ShareShare
ReportReport
Posted on by RR-01030612-0 202
Hello Community,

While testing with a new company in the sandbox environment, we encountered issues with tax calculations.
The tax component code was unavailable, and manual entry through the page did not update it.
 
As a workaround, we imported the corresponding JSON file from a working environment.
Following this, the page displayed the below error:
“The record in table 'Script Symbol' already exists. Identification fields and values: Symbol Type='Tax Attributes', ID='1'.”

We also performed a version upgrade to 26.3, but the issue persists.

To further investigate, we created another company and tested the components again—and the same issue occurred.
Screenshots have been attached.

We would appreciate your suggestions for resolving this issue.

Thanks in advance!
Categories:
Dynamics 365 Business Central
components-preliv...
components-preliv...
components-preliv...
I have the same question (0)
  • Suggested answer
    Sumit Singh Profile Picture
    Sumit Singh 10,078 on at
     Reasons
    1. Duplicate Tax Attribute Symbol
    • The Script Symbol table is used internally by Business Central to store metadata for tax configurations, especially in localized environments like India.
    • The error indicates that a Tax Attribute with ID '1' already exists.
    • This typically happens when:
      • A JSON configuration file is imported multiple times.
      • A company is copied or recreated without clearing system tables.
      • A version upgrade retains old metadata but tries to reinitialize it.
    2. Manual Entry Not Updating
    • Manual entry via the UI may not trigger the necessary backend script to update the Script Symbol table.
    • This causes inconsistencies between what’s visible and what’s stored internally.
    Recommended Resolution Steps
     Option 1: Clear Duplicate Entry (Safest in Sandbox)
    If you're in a sandbox, you can safely clear the duplicate entry:
    1. Go to Table Information via Ctrl+Alt+F1 or use the Web Client Inspector.
    2. Search for the Script Symbol table.
    3. Use Configuration Package or Edit in Excel to:
      • Export the table.
      • Identify the duplicate entry (Symbol Type='Tax Attributes', ID='1').
      • Delete it manually.
    4. Re-import the JSON file or reconfigure the tax component.
    Note: This should only be done in a sandbox or test environment. In production, consult your partner or Microsoft support.
    Option 2: Create a Clean Company
    Since you've already tried this but the issue persists, ensure:
    • You do not copy data from the old company.
    • Use Assisted Setup to initialize GST configuration.
    • Avoid importing JSON until the base setup is complete.
     Option 3: Use Configuration Package for Tax Setup
    Instead of JSON, use a Configuration Package to import:
    • Tax Component
    • GST Posting Setup
    • Tax Jurisdiction
    • Tax Group
    This gives you more control and avoids backend script conflicts.
    Best Practices
    • Always test tax setups in a clean sandbox before migrating to production.
    • Avoid re-importing JSON files unless necessary.
    • Use version-specific localization guides for India (v26.3 has changes in tax metadata handling).
    Note: This response was created in collaboration with Microsoft Copilot to ensure clarity and completeness. I hope it helps to some extent.
    Mark the Answer as Verified if this is Helpful.
     
  • Suggested answer
    DAnny3211 Profile Picture
    DAnny3211 11,397 on at

    Hi there,

    This issue seems related to a conflict in the Script Symbol table when importing tax configuration data manually via JSON. The error:

    "The record in table 'Script Symbol' already exists. Identification fields and values: Symbol Type='Tax Attributes', ID='1'"

    suggests that the import is trying to create a record that already exists, which is common when reusing configuration files across environments.

    Here are a few suggestions to resolve it:

    1. Avoid Duplicate Imports:

      • Before importing the JSON file, check if the tax component already exists in the target environment.
      • If it does, either delete the existing record or modify the JSON to use a different ID.

    2. Use Assisted Setup or Configuration Packages:

      • Instead of manual JSON import, try using Assisted Setup or Configuration Packages to initialize tax components. These methods are more controlled and reduce the risk of conflicts.

    3. Clean Sandbox Environment:

      • If possible, test in a fresh sandbox company without any prior tax configuration to avoid residual data conflicts.

    4. Check for Extension Conflicts:

      • If you're using custom extensions or localization packs, ensure they are compatible with version 26.3 and not interfering with tax setup.

    Let me know if you'd like help reviewing the JSON file or setting up the tax components from scratch!

    Please verify if this response was helpful.

    Best regards!

  • RR-01030612-0 Profile Picture
    RR-01030612-0 202 on at

    Thank you Mr. DAnny3211 and Mr. Sumit Sigh for the valuable responses,

    We created and tested a new company in the sandbox environment, and the same issue occurred: the tax components are not present in the GST Posting Setup.

    We attempted to manually enter the components through the page, but the entries were not saved. Upon refreshing the page, the newly entered components disappeared.

    This primary error led us to import the JSON file. However, the actual issue remains—the tax calculation is not working in purchase, sales, or other transactions, and the components are still missing from the GST Posting Setup.

    Screenshot are attached.

    Regards,
    Remya
    components-preliv...
    purchase order-1.png

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,229

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,867 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,153 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans