Open IuliiaHerets opened 1 week ago
Triggered auto assignment to @slafortune (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.
We think that this bug might be related to #wave-control
@slafortune FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
Edited by proposal-police: This proposal was edited at 2024-10-09 21:40:29 UTC.
Add an additional logic to line:
const isCollectWorkspace = policy.type === 'team';
if (isCollectWorkspace && ['quickbooksOnline', 'xero', 'quickbooksDesktop'].includes(connectionName)) {
optimisticData.push({
onyxMethod: Onyx.METHOD.MERGE,
key: `${ONYXKEYS.COLLECTION.POLICY}${policyID}`,
value: {
areReportFieldsEnabled: false,
pendingFields: {
areReportFieldsEnabled: CONST.RED_BRICK_ROAD_PENDING_ACTION.UPDATE,
},
},
});
successData.push({
onyxMethod: Onyx.METHOD.MERGE,
key: `${ONYXKEYS.COLLECTION.POLICY}${policyID}`,
value: {
pendingFields: {
areReportFieldsEnabled: null,
},
},
});
failureData.push({
onyxMethod: Onyx.METHOD.MERGE,
key: `${ONYXKEYS.COLLECTION.POLICY}${policyID}`,
value: {
areReportFieldsEnabled: policy?.areReportFieldsEnabled,
pendingFields: {
areReportFieldsEnabled: null,
},
},
});
}
BE should fix it as well. In detail, when we disconnect, BE needs to turn off report field feature as well.
Job added to Upwork: https://www.upwork.com/jobs/~021844128989949063152
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allgandalf (External
)
@slafortune , a thought:
report fields
unless the workspace itself in on a control plan
, it's a control plan
only feature, can you take it to our slack #expense
channel and tag me there? the expected result doesn't seem right, please tag me there too@slafortune, @allgandalf Eep! 4 days overdue now. Issues have feelings too...
bump on ^ @slafortune
Report fields are a control feature, moving this to #expense.
Perfect since everything Collect or Control is going to the Expenses Project
Sorry for my delay @allgandalf
We should never allow the toggle of report fields unless the workspace itself in on a control plan, it's a control plan only feature, can you take it to our slack #expense channel and tag me there? the expected result doesn't seem right, please tag me there too
Report fields unrelated to any accounting integrations are not supported on the Collect workspace This bug had been related to the Collect workspace project since the QBO connection is allowed on the Collect workspace - which allows for report fields.
if connected to an accounting integration that is allowed on the collect workspace - report fields are enabled. When disconnecting - report fields should be removed.
Sorry - some keyboard shortcut closed that 😱
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
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.0.46-1 Reproducible in staging?: Y Reproducible in production?: Y Issue reported by: Applause Internal Team
Action Performed:
Precondition: user has Collect workspace.
Expected Result:
Report fields, as feature, available in Control workspace, disappeared from LHN.
Actual Result:
Report fields stays in LHN. User can access tab and add report filed to a collect workspace.
Workaround:
Unknown
Platforms:
Screenshots/Videos
https://github.com/user-attachments/assets/cbbe90ce-9229-4bc8-bd13-f8097e24a664
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @allgandalf