Error encountered in testing newly created table in Framework Manager

[DiGzâ„¢747]

Hi Guys,

Here's my issue.  We've just import a newly created table in the datawarehouse.  Relationships with other tables were successfully created.  The package was successfully published.  But while doing test run on the new table through Report Studio, I encounter the error below.
 
"<message code="-16"severity="error"title="QE-DEF-0459 CCLException"type="general">RQP-DEF-0177 An error occurred while performing operation 'sqlPrepareWithOptions' status='-16'.
UDA-SQL-0353 An error was detected while processing the SQL request.
ERROR:  Relation 'pcdw_fact_chargeability_goal' does not exist"

Is there something that I missed doing in the Framework Manager? Hope anyone of you guys could help me sort this thing out...

Thanks alot and God bless....
DiGz

[Luhaine]

"Relationships with other tables were successfully created." vs "Relation 'pcdw_fact_chargeability_goal' does not exist"

Does that mean that you let FM generate your relationships? If so, go and check them manualy to make sure it is (they are) indeed correct. I avoid having FM generate my relationships when I can since my experience with applications interpreting relations between tables has not been without its problems.

[DiGzâ„¢747]

Hi Luhain,

Thanks for your quick response.  As for your question, I manually created the relationships of the pcdw_fact_chargeability_goal table with the other tables.  Those relationships were patterned from the existing relationships of an old table.  By the way, the new table does not have data yet. But, I believe that is should not be an issue. Right? What do you think is the problem here?

Thanks again,
DiGz

[Luhaine]

I don't think that the table having no data should be an issue in this case, but the possibility should be relatively easy to eliminate, which warrants checking it out. The only situation I can imagine where data could be an issue if there actually was a piece of data referencing to a field in the linked table from another table where it expects to find data, but the error description doesn't really match that.