It's all about the answers!

Ask a question

RS data source Lifecycle Query engine can not be refreshed


Kim Soederhamn (1.5k23638) | asked Jan 11, 2:48 a.m.
edited Jan 11, 8:06 a.m.

Sometimes you may not be able to refresh a data model for a data source.


This is totally normal for a "Lifecycle Query engine scoped by a configuration" - however you should normally be able to refresh the standard "Lifecycle Query Engine" data source. But you could end in a situation where the button is grayed out and you find something like:
    No corresponding non-config data source. Ignoring data source:
in the rs.log

Accepted answer


permanent link
Kim Soederhamn (1.5k23638) | answered Jan 11, 2:51 a.m.
edited Jan 11, 8:05 a.m.

 This can be caused by the field

require a configuration to run a report - accidentally being set on the Lifecycle Query Engine data source.

require configuration
This flag should only be set for the "Lifecycle Query Engine Scoped By a Configuration" data source.

Uncheck the field and save the datasource.


Ralph Schoon selected this answer as the correct answer

One other answer



permanent link
David Honey (4856) | answered Jan 11, 5:28 a.m.
JAZZ DEVELOPER
edited Jan 11, 5:29 a.m.
Just to expand on Kim's advice.

Normally, when you setup Report Builder and there are one or more project areas that have opted in for configuration management, three data sources are created by the setup wizard:
  1. Data warehouse
  2. Lifecycle Query Engine
  3. Lifecycle Query Engine scoped by a configuration
The Lifecycle Query Engine and Lifecycle Query Engine scoped by a configuration data sources for a given instance of LQE form a pair. They share the same meta data. If you refresh the type system model for Lifecycle Query Engine the meta data it produces is also used for the Lifecycle Query Engine scoped by a configuration data source. So when you have such a pair, you only refresh the Lifecycle Query Engine data source. In recent versions of report builder, the refresh option for the Lifecycle Query Engine scoped by a configuration data source is disabled to prevent users from unecessarily refreshing the configuration enabled one of a pair.

As Kim stated, if you have a configuration enabled data source, this should always be one of a pair of data sources for the same LQE instance. If someone has accidentally modified the Lifecycle Query Engine data source to be configuration scoped you should fix that user error by unchecking that option.

Your answer


Register or to post your answer.