Here’s some things to consider if you or other users aren’t seeing some or any of the imported data you expected to see when you opened views to work with the data.
Make sure the import is done processing. Check for a Completed status in the Data Import list window.
Make sure the view includes the dimensions impacted by the import and you are looking at the time period(s) for which data was imported.
Verify the user has read access to all the data – in this case, to the dimensions where data got imported. That can be verified by administrators, who can look at a user’s role and user profile.
The data may have ended up in a dimension’s default value of “?”. If the view where you expected to see the data has a filter applied to filter out the “?” default value, remove the filter and look at the default value. Then see if the imported data displays in the view for that default value. See also Why Did Import Data Get Added To A Dimension’s Default Value ‘?’ Member?.
To further investigate what got imported, review details in the import processing report and compare them to your import file or table. The report tells you which tells got imported and how many rows were imported. See Review Processing Details For A Data Import.
It’s possible the import source had a null row – Data Import will stop looking for data to import once it finds a null row. Look at your import source to verify it doesn’t have any null rows. Those are rows without any data in them. Compare the number of rows in your file or table to the “Number of Rows Imported” information in the processing report.
You may have accidentally set some columns you intended to import as ones to “Ignore” when you were mapping the data. Compare the columns in your import source to the Data Mapping section of the processing report.