Data refresh for co-mingled sources

[tomascid]

I have a dashboard I'm developing for a client. It has two major data sources:

1. Data from an API (which my client can access) and

2. Data from my machine (which my client can't access). 

Problem is that I have created a few queries that merge/intermingle data from the two data sources. Let's call these:

Query 1 (all data from source 1 [API, client can access])

Query 2 (all data from source 2 [non-API, client can't access], and

Query 3 (combination of queries 1 and 2)

I turned off "Include in report refresh" for query 2 but left it on for Queries 1 and 3. I thought it would be smart enough to know that I told it not to refresh query 2, so when it comes time to refresh Query 3, only refresh the data from Query 1, not 2.

It doesn't seem to be doing that - instead, on my client's machine, it throws an error and doesn't update any sources because it says, under Query 3, "I can't find or update Query 2". I thought it would be smart enough to know that we imported data for Query 2, just use the existing data already loaded, don't try to refresh.

Has anyone had this issue? Any suggestions, other than never intermingling data from sources that can and cannot refresh?

[mahoneypat]

Since query 3 is included in refresh, it triggers the refresh on query 2.  You may have to export your query 2 data as csv so your client can refresh against that.

If this works for you, please mark it as the solution.  Kudos are appreciated too.  Please let me know if not.

Regards,

Pat