Tabular Reports in Journey Orchestrator
None
Hi All,
One of the frequently asked feature in Journey Orchestrator has been the need for sending tabular reports in emails.
We are looking at addressing that use case using the following approach -
a. You will be able to use any of the tabular reports configured as part of email configuration.
b. You will have two options- CSV/Inline Option for sending a tabular report.
- CSV option is aimed at use cases where there are many rows and columns and the data is of high volume.
- Inline Option is aimed at use cases where the data you want to share are simple tabular reports in email with very few rows and columns.
c. For inline option, a maximum of 5 columns and 20 rows will be allowed in tabular reports.If the report exceeds this limit , then the report will be sent as CSV to the recipient.
[i]We are looking for feedback on the above proposal and guide us with respect to whether the above approach will meet the use case of tabular reports. [i]Are there any other use cases which you felt we have missed?
As we are in the early stages of this design, things might become flexible in the future based on other considerations or use cases. :)
Thanks
Abhishek S
One of the frequently asked feature in Journey Orchestrator has been the need for sending tabular reports in emails.
We are looking at addressing that use case using the following approach -
a. You will be able to use any of the tabular reports configured as part of email configuration.
b. You will have two options- CSV/Inline Option for sending a tabular report.
- CSV option is aimed at use cases where there are many rows and columns and the data is of high volume.
- Inline Option is aimed at use cases where the data you want to share are simple tabular reports in email with very few rows and columns.
c. For inline option, a maximum of 5 columns and 20 rows will be allowed in tabular reports.If the report exceeds this limit , then the report will be sent as CSV to the recipient.
[i]We are looking for feedback on the above proposal and guide us with respect to whether the above approach will meet the use case of tabular reports. [i]Are there any other use cases which you felt we have missed?
As we are in the early stages of this design, things might become flexible in the future based on other considerations or use cases. :)
Thanks
Abhishek S
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Our executives enter in a weekly Timeline entry that we've created a Dashboard for. But because the posts and can be rather long at times - they have to export. With the new proposed feature - we could automate that report instead - which would be a huge win!
I agree with the size limit - what you proposed works much like when exporting an Excel items from Reporting. If small enough - it will open right for you. But large enough - and it's emailed to you. Consistency :)
But to also be able to have the ability to NOT have to have linked to Account, would be awesome. For the example, the people that would receive the excel report of the executive - may not have posted or be tied to an account. It would be internal only.
In particular I don't mind the CSV report, I've had to build scheduled reports from SFDC in some cases, and would prefer not to have to do that
Is there currently any workaround for being able to insert simple tabular reports in an email assist?
This is such a common use case to use tabular reports in JO. I have hit a roadblock so many time trying to use JO and gave up because we cannot effectively use tabular reports. Any idea if there is a workaround or feature roll out plan on this one?
Hi@abhishek_sivaraman . I know that you can send tabular reports and it limits the inline view to 5 columns and 20 rows of data. Though, there is no CSV file upload to the email when there is this much data. When trying to send a tabular report that has this much data it defeats the purpose if the recipient cannot get all of the data I am trying to send. Is there any update on the attachment of the CSV when there is more data than what can be viewed inline?
Currently JO does NOT provide any feedback on the true # of retrieved rows for embedded tabular reports for any one company. I think after participants are brought into a program that the report filtering/snapshot job should do a check on # of filtered rows/ # of displayed rows and whether participant(s) were seeing all of the report info pertinent to them. If the amount of info for a tabular report exceeds the limitation I think we need to add in an option that would automatically attach a tabular report CSV onto the email sends for participants where the 5x20 limitation is exceeded.
Also, I think it would be useful to see # of filtered rows/ # of displayed rows when previewing an email step with an inline tabular report.
These 20 x 5 limitations make this pretty useless.
Either revamp the “success plan PPT reports” to broaden its use with an option NOT to break data down by company and just to embed reports into a PPT that can be sent out on a schedule (therefore removing the need to suffer the 20x5 issue), or remove limits on tabular reports in email body.
Feature doesn’t fulfill its purpose currently.
We are unable to add tabular reports to Journey Orchestrator using Nxt. Will this be implemented in the future?
Could you please share the typical number of records you are looking to embed within an email body?
Subsequently, we are also looking into providing further customisation options such as automatically shifting to an attachment when the tabular report crosses the max row threshold. I have added embedded reports enhancements to our backlog for prioritisation
Could you please share the typical number of records you are looking to embed within an email body?
Subsequently, we are also looking into providing further customisation options such as automatically shifting to an attachment when the tabular report crosses the max row threshold. I have added embedded reports enhancements to our backlog for prioritisation
Thank you. The reports we are trying to embed for our first iteration of usage are very small. When you say it will be limited to 100 rows, is that from the table itself, or the table filtered for recipients? If it is filtered by recipients, what happens if 1/100 recipients would have more than 100 rows? Does the single email fail, the entire program fail, or the embedded report for 1 recipient fail, for example? How is the Admin notified?
Today even with the smallest of tabular reports, we see this error when embedding:
Today If there are more than 20 rows in the tabular report, currently the extra rows are truncated in email body. The email is still sent out to the recipient with 20 rows.
However, as a workaround if the same report is embedded as an attachment, full data is included for all the rows
Today If there are more than 20 rows in the tabular report, currently the extra rows are truncated in email body. The email is still sent out to the recipient with 20 rows.
However, as a workaround if the same report is embedded as an attachment, full data is included for all the rows
Should I open a support ticket for the above error? I cannot embed any tabular reports, even 1 with 1 row and 2 columns. I am using Nxt and Horizon Reporting.
Please open a support ticket, this seems to be an error