Some missing information from your question that would help.
1) What do you mean by "custom view"? Do you mean a view you have created in your database, or something else?
2) Are you using Tableau Server? If so, do you have a schedule refresh of the data source so that your extract gets updated automatically? Or are you ONLY in Tableau Desktop, and the extract refresh is a manual process?
To answer what I think you are asking:
There are 2 different kinds of Refresh in Tableau.
1) A data extract refresh - this is what you are describing in your question.
2) A Workbook refresh of the extracted data. My guess is that this is your problem. Once the data extract has been refreshed, you need to force your workbooks and visualizations to reload the refreshed data. If you are looking at a published workbook on Tableau Server, the "Refresh" link in the toolbar on the left side of the viz is what you want.
I hope you are talking custom views in tableau server like below
If that's the case change the view to original and check if the data is still not there or not because custom view you created is on the top of original view with some filters may be that's causing the problem
Check all the filters as well
Hope this kindly mark this as correct/helpful to close the thread
Yes I am talking about custom views created at workbook level.
We have refreshed workbook after changes and all changes reflecting in original view correctly.
But views created earlier still shows old hierarchy and even I clicked on Refresh Button.I can create new View from original view and save. but question here we have lot of users created their own views and this impacted all (I just gave one example but hierarchy changed for many countries!!).
I hope you got my situation.
I am talking about the custom views created at the tableau server (Workbook level) and extract refreshed successfully and we can see updated data in original Views.
Just curious... Were you ever able to resolve the issue you were having with custom views not refreshing? We are starting to use them more here as well and running into the same issue.