You can create a SAS Visual Data Builder query that includes other existing queries as input tables. When you promote this type of query to a different environment, you might see an error that is similar to this one in the import log: 

The error message might also show a blank query name and null for the reason. 

This problem can occur when the query that you are promoting does not reference the dependent query by its current ID. Queries that are in this broken state show a blank Location field on the Inputs pane. In the following display, SubQ is the dependent query that is being used as input to a query named ParentQ. The ParentQ query is in a broken state, which can be seen by the blank Location field for SubQ.

A query ID can be overwritten if you import a copy of the query and overwrite the existing copy. Each time that you import and overwrite the current copy of the query, a new entry is added to the VDBServices database with a new ID. In this scenario, only the most current ID is valid. You can promote only those queries that reference the current ID of the dependent query. 

If you encounter this problem, edit the main query in the source environment to remove the dependent query, and then add the dependent query again so that the current ID is used. After making the change, verify that the Location field for the dependent query is populated with a valid path. (If the Location field remains blank, save the query, close it, and then reopen it.) To avoid the issue, do not overwrite queries that are being used as dependent queries. The following display shows a red exclamation point on the query named SubQ, which indicates that the query already exists and will be overwritten. 

Click the Hot Fix tab in this note to access the hot fix for this issue.

The hot fix does not enable you to overwrite dependent queries, but you are more explicitly warned that the query exists and that you must delete the query before continuing. In the case of a dependent query, you must delete both the main query and the dependent query. Then, re-import the main query with its dependent query. If you only delete and then re-import the dependent query, you will still encounter the issue described in this SAS Note. 

Operating System and Release Information

A fix for this issue for SAS Visual Analytics 7.51 is available at: