Certinia - Dimension setting reverts to the default value

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.4.0-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #91221
Email or phone of affected tester (no customers): applausetester+ag050626.2@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11/ Chrome, Samsung S23FE/ Android 16, iPhone 13 Mini/ iOS 26.3
App Component: Workspace Settings

Action Performed:

Preconditions: Have a control workspace with the Accounting feature enabled.
Use an Expensifail account.

1. Go to staging.new.expensify.com
2. Log in as workspace admin
3. Go to workspace settings > Accounting
4. Connect to Certinia
5. Go to Import and change any dimension setting to Tags or Report Fields
6. Close the RHP
7. Wait until sync completes
8. Go again to Import
9. Go to the edited dimension

Expected Result:

The dimension setting remains as selected in step 5.

Actual Result:

The dimension setting reverts to the default value “Do not map”.
This occurs only the first time a dimension setting is changed.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7173092_1780702571051.dimension_setting_not_updated.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7173092

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/a6fa2ac538e8ad2533c9f3082a827df7c0497cf03653ea0f7c3dcd3bd3ea10c3

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #91221

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[godzillaxbox19982014-lgtm]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Certinia-Dimension setting reverts to the default value

What is the root cause of that problem?

I traced this to the path that handles workspace name, S23FE, iOS:

• src/pages/workspace/accounting/certinia/CertiniaExistingConnectionsPage.tsx:22 (matching code path): type CertiniaExistingConnectionsPageProps = PlatformStackScreenProps<SettingsNavigatorParamList, typeof SCREENS.WORKSPACE.ACCOUNTING.CERTINIA_EXISTING_CONNECTIONS>;
• src/pages/workspace/accounting/intacct/import/SageIntacctUserDimensionsPage.tsx:93 (settingsPendingAction): pendingAction={settingsPendingAction(['${CONST.SAGE_INTACCT_CONFIG.DIMENSION_PREFIX}${userDimension.dimension}'], config?.pendingFields)}
• src/pages/workspace/accounting/intacct/import/SageIntacctUserDimensionsPage.tsx:101 (areSettingsInErrorFields): areSettingsInErrorFields(['${CONST.SAGE_INTACCT_CONFIG.DIMENSION_PREFIX}${userDimension.dimension}'], config?.errorFields)
• The local evidence matches this recurring failure shape: shared workspace list builds options without the same eligibility filter as another workspace surface. Here, src/pages/workspace/accounting/certinia/CertiniaExistingConnectionsPage.tsx:22 and src/pages/workspace/accounting/intacct/import/SageIntacctUserDimensionsPage.tsx:93 do not agree on the same workspace name, S23FE, iOS value, so the user-visible path can show a missing or stale state even though nearby data already has the needed context.

What changes do you think we should make in order to solve the problem?

• Update src/pages/workspace/accounting/certinia/CertiniaExistingConnectionsPage.tsx:22 to derive workspace name, S23FE, iOS from the workspace setup and policy state that owns this flow before the value is consumed.
• Carry the same normalized value through src/pages/workspace/accounting/intacct/import/SageIntacctUserDimensionsPage.tsx:93; that follows the safer family move to move the rule into the shared selector/helper, so the write/optimistic/read paths agree instead of only changing the visible component.
• Keep the change inside the Workspace, Policy, Categories, Tags, Rules surface and avoid changing account/admin permission surfaces, policy owner/current-user exceptions.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

1. Add or update a regression in tests/unit/Policy*.ts for the exact issue flow: Certinia-Dimension setting reverts to the default value.
2. Cover the counter-case near src/pages/workspace/accounting/certinia/CertiniaExistingConnectionsPage.tsx:22 so valid existing workspace name, S23FE, iOS behavior still works.
3. Manually repeat the issue steps after the patch and confirm the visible state/action is no longer stale.

What alternative solutions did you explore? (Optional)

• I would not add a broad new condition outside these referenced paths; the safer fix is to keep workspace name, S23FE, iOS consistent at the first read/write boundary shown above.