Hi @Gary Jarvis, and thank you for bringing up your concern! I would like to ask, for clarity, where you are seeing this change. Is this in New Reports or the Automation App?

Additionally, if you could provide screenshots, this would be a great help! We have not seen other reports of this yet, and would like to investigate this issue for you.

It is in new reports

lets take one example: the field name in the CSV was “Branches” now it has changed to “Branch path”

Old

New

and there are several other fields effected

@elliott.vickrey We are also affected by this issue. The alterations to field names in our reports have affected the transaction reports we send to Netsuite for accounting purposes. Unfortunately, we were unaware of these changes, leading to reports with missing data. This marks the second occurrence of such an issue impacting our reports. It would greatly benefit us if we could receive notifications about any field name changes in the reports, allowing us to take necessary precautions to prevent these changes from affecting our reports in the future.

Please see the recent field change below:
 

• Discount to Transaction Discount
• Price to Item Price
• Total Price to Total Transaction Price
   

  

  
   

  

   

I can confirm that this is negatively impacting our data feeds to our customers and partners as well.  Advance notice of changes to fields names in reporting is absolutely necessary to avoid this.  We have to reset all of our Power BI fields to align.

@neil.kremer FYI

We raised this internally.

Yikes…changes to reports definitely need to be reported almost like changes to APIs with the alerts and notice in advance. So many people leverage them similarly and build complex business processes off of them. Some can abstract out the titles into their own, but not everyone has those tools plus it then makes every report use a more complex setup. 

The product owner confirmed there will be no more changes without a previous notification (similar to what we do with the API’s). I hope this helps, and we apologize for any inconvenience.

Thanks @rani.alsous 

@rani.alsous thank you for the update.

The branch field name change has impacted our reporting as well. All queries that rely on that field must be manually updated. The Salesforce synchronization could also be impacted by a branch field change,  I need to investigate to confirm. API calls are another risk. “Branch” touches many aspects of our systems and teams, so it is crucial to have that information communicated in advance to avoid disruption.

Can we please have a complete list of all field name changers that were made?

@rani.alsous - I have the same ask as above. Can you please provide a complete list of all field name changes that were made?

Thanks

Hello everybody, I’ve already requested the information internally, and I will provide updates in this thread, as soon as I have any news.