[$250] BUG: Sage Intacct subsidiary is not shown on Connections card under Sage Intacct logo

[dylanexpensify]

Testing doc: here (request, will share)

Pre-testing steps

• Make sure the email address does not already have existing workspaces/policies
• Make sure emails sent to the testing email addresses go to an inbox you can access to validate your account(s)
• Create a new collect policy on OldDot and;
• Set the approval mode to “submit and approve”
• Enable scheduled submit with a frequency of Daily or “slower”
• Invite an additional user to the policy to play the member role in these testing flows
• Run the script stated here to enable workspace chat creation for a paid plan.

Pre-testing steps

• Make sure that your test account is on the intacctOnNewExpensify beta
• Make sure you have Sage Intacct web services user ID, password and Company ID to initiate a connection
• Make sure you create a new workspace/policy for each test run
• Make sure emails sent to the testing email addresses go to an inbox you can access to validate your account(s)

Steps:

1. Head to Workspace settings
2. Head to Accounting
3. Under Sage Intacct Connection click Connect
4. Enter valid credentials

Expected result: Once connected, the Sage Intacct subsidiary is shown on Connections card under Sage Intacct logo + Last synced message
Actual result: The Sage Intacct subsidiary is not shown on Connections card under Sage Intacct logo + Last synced message

Screenshot:

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~015bae9383e2075bb8
• Upwork Job ID: 1815835932579772267
• Last Price Increase: 2024-07-23
• Automatic offers:
• paultsimura | Reviewer | 103311605

Issue Owner

Current Issue Owner: @greg-schroeder

[melvin-bot]

Triggered auto assignment to @greg-schroeder (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~015bae9383e2075bb8

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @paultsimura (External)

[kabeer95]

Proposal

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

The problem we are trying to solve is that the Sage Intacct subsidiary is not shown on the Connections card under the Sage Intacct logo after connecting to Sage Intacct from the Workspace settings.

What is the root cause of that problem?

The root cause of this problem is likely due to an incorrect implementation of the Sage Intacct API or a misconfiguration of the connection settings, which prevents the subsidiary information from being retrieved and displayed on the Connections card.

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

To solve this problem, we need to review and adjust the Sage Intacct API implementation to ensure that it correctly retrieves and displays the subsidiary information on the Connections card. Specifically, we should verify that the Sage Intacct web services user ID, password, and Company ID are correct and properly configured, check the XML API calls to ensure that they are correctly formatted and include the necessary fields to retrieve the subsidiary information, and review the code that handles the connection to Sage Intacct and the display of the Connections card to ensure that it is correctly parsing and displaying the subsidiary information.

// Verify Sage Intacct credentials and connection settings
const sageIntacctCredentials = {
  userId: 'your_user_id',
  password: 'your_password',
  companyId: 'your_company_id'
};

// Set API endpoint and headers
const endpoint = 'https://api.intacct.com/ia/xml/xmlgw.aspx';
const headers = {
  'Content-Type': 'application/xml',
  'Authorization': `Basic ${sageIntacctCredentials.userId}:${sageIntacctCredentials.password}`
};

// Set XML payload to retrieve subsidiary information
const payload = `
<?xml version="1.0" encoding="UTF-8"?>
<request>
  <control>
    <senderid>${sageIntacctCredentials.companyId}</senderid>
    <password>${sageIntacctCredentials.password}</password>
    <controlid>string</controlid>
    <uniqueid>false</uniqueid>
    <dtdversion>3.0</dtdversion>
  </control>
  <operation>
    <authentication>${sageIntacctCredentials.companyId}</authentication>
    <get>
      <object>subsidiary</object>
    </get>
  </operation>
</request>
`;

// Send request to Sage Intacct API
const response = await fetch(endpoint, {
  method: 'POST',
  headers,
  body: payload
});

// Parse response to retrieve subsidiary information
const subsidiaryInfo = await response.xml();
if (subsidiaryInfo) {
  // Display subsidiary information on Connections card
  console.log('Subsidiary information:', subsidiaryInfo.text);
} else {
  console.error('Failed to retrieve subsidiary information');
}

[greg-schroeder]

Proposal review underway

[paultsimura]

@greg-schroeder not much to review here. Unfortunately, @kabeer95's proposal looks like a generic GPT-generated answer (they've been warned about such proposals in the past, but nothing really changed): generic self-repeating sentences with no App-specific code links, etc.