Temporary tables for reporting

[SM16]

We have a requirement where the user wants to report on the data which is not in ServiceNow. They are ready to share the data in flat file which can be imported into ServiceNow for reporting purposes.

• Do you think its wise to create tables for those flat files, just for reporting purposes considering tables are licensed now?
• Can we use Import set table accepting the risk that data stays only for 7 days and then they need to report the fresh data (Once in a week)
• Even if we use import set table, we need to create required data type fields like Reference or List or Boolean so that proper reporting can be supported via ServiceNow. Is it worth to do this?
• Has anybody faced this kind of sitation and what was your approach towards this?

[AndersBGS]

Hi @SM16 ,

You can create a report directly from an Excel file by import directly into the report designer. You can see further here: https://docs.servicenow.com/bundle/vancouver-now-intelligence/page/use/reporting/task/create-report-...

If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.

Best regards

Anders 

[Jaspal Singh]

Hi, 

Is ServiceNow the only system being used in client environment? If not, and still ServiceNow is being is looked at to be go-to solution then I would think it is an opportunity to explore other areas of ServiceNow (PA - if needed in the longer run). This will also increase ServiceNow demand in the organization.

Yes, creating tables will have some license implications however it is always better to check with ServiceNow Account representative to understand costing.

For your case, you can start with few questions 

1. How many fields, records are expected (OOB 50 for custom tables)

2. What is the trend

3. How frequently data will be imported, etc.

In case if there are very less cost implications then instead of data load you can plan to integrate and push the data from ABC system to ServiceNow. Well, this is only after you decide on looking at cost and budgeting.

If there happens to be other reporting tools you can suggest that route instead as license and maintainance can be an over-head.