-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Comments
@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 |
Hi @thienlnam. I'll check this out today and follow up! |
@thienlnam Can you please explain what details from the |
If it has the deletable field set, we can modify the report title - if not, we would not be able to |
Added these changes in #34483 |
@allroundexperts, @thienlnam Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@allroundexperts, @thienlnam Still overdue 6 days?! Let's take care of this! |
@thienlnam I think this can be closed since the required changes were merged in #34483 |
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
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
The text was updated successfully, but these errors were encountered: