Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different handling for text_title report fields #35043

Closed
thienlnam opened this issue Jan 24, 2024 · 8 comments
Closed

Different handling for text_title report fields #35043

thienlnam opened this issue Jan 24, 2024 · 8 comments
Assignees
Labels
Daily KSv2

Comments

@thienlnam
Copy link
Contributor

thienlnam commented Jan 24, 2024

The text_title report field are inherently different than the other report fields. They're the only report fields that use formula values and are an actual property on the report itself. We'll need to handle this differently from other report fields.

The policyReportFields_policyID onyx key will tell us if the following parameters about the report title

  • Can it be modified?

When this field exists on a policy, we will show the title report field. However, it's value is derived from the reportName of the report, and when you try to update it - you will have to call the API with these parameters

command: RenameReport
reportID: 6279759066218631
reportName: "Expense Report 2024-01-24 121331"

We'll use the details from the policyReportFields_policyID onyx key to see if we can modify this field.

We will no longer need to pass the text_title to Report_SetFields

You should be able to test this by creating a workspace chat in NewDot with these steps

To enable this "beta" for any given policy:

Go to OldDot and open the settings for the Collect/Control policy

In the JS console with the policy open do:

p = Policy.getCurrent();
p.policy.isPolicyExpenseChatEnabled = "true";
p.save();
This will make it so that any user you invite to that policy going forward will have a Workspace Chat created in NewDot for that policy. It will not retroactively create a workspace chat for the policy owner or any other user that was already a member of the policy before you enabled the beta.
@thienlnam
Copy link
Contributor Author

@allroundexperts Let me know if this makes sense, or if there's anything I can clarify here - the BE is already set up for this command

@allroundexperts
Copy link
Contributor

Hi @thienlnam. I'll check this out today and follow up!

@allroundexperts
Copy link
Contributor

We'll use the details from the policyReportFields_policyID onyx key to see if we can modify this field.

@thienlnam Can you please explain what details from the policyReportFields_policyID collection would determine if we can edit the title or not?

@thienlnam
Copy link
Contributor Author

If it has the deletable field set, we can modify the report title - if not, we would not be able to

@allroundexperts
Copy link
Contributor

Added these changes in #34483

@melvin-bot melvin-bot bot added the Overdue label Jan 31, 2024
Copy link

melvin-bot bot commented Feb 1, 2024

@allroundexperts, @thienlnam Whoops! This issue is 2 days overdue. Let's get this updated quick!

Copy link

melvin-bot bot commented Feb 5, 2024

@allroundexperts, @thienlnam Still overdue 6 days?! Let's take care of this!

@allroundexperts
Copy link
Contributor

@thienlnam I think this can be closed since the required changes were merged in #34483

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Daily KSv2
Projects
None yet
Development

No branches or pull requests

2 participants