BODI-1111073 Error while Validating

dataservices job design
1

hi friends,

I’m new to BODS and we have recently upgraded to BODS 4.1 version from 3.2 and we are facing an issue while validating one of the query transform. In that query transform, we have used a condition like ‘Query.FISCAL_YEAR in (‘2013’, ‘2014’)’ and in the following query transform ‘Actuals_GrpBy’, we have used GroupBy functionality. This didn’t cause any error in 3.2 version. I couldn’t understand the fact that even though we removed the year filter in the previous transform, while validating we can still view the error. The exact error message is:

[Query:Actuals_GrpBy] Invalid query <"2FY=2013, 2014>. (BODI-1111073)

Can anyone kindly look into issue and suggest an opinion on solving this.

Attached screenshots in the document

Thanks,
Nova
error_while_validating.doc (117.0 KB)

novasuper007 (BOB member since 2010-02-25)

2

Looks like Actuals_GrpBy Query Transform has something flawed or something got erased or something. Your screenshot doesn’t show the exhaustive column list of that last query transform. You will have to further look into that transform further.

ganeshxp :us: (BOB member since 2008-07-17)

3

Did the filter somehow make it into the FROM clause? Look at the expressions on the FROM tab.

eganjp :us: (BOB member since 2007-09-12)

4

hi Ganesh,

For some reason, the error didn’t show off today, I just reopened the last transform and checked whether fields are correctly mapped. Then closed it re-validated, guess what the error didn’t show up. I can’t understand this strange behaviour in the BODS designer (4.1v).

Anyways, I don’t see the issue anymore. Once again, I appreciate all your suggestions & efforts.

Thanks,
Nova

novasuper007 (BOB member since 2010-02-25)

5

Did you save the Dataflow at any time?

eganjp :us: (BOB member since 2007-09-12)

6

Yes Jim,

I did save the data flow.

Thanks,
Nova

novasuper007 (BOB member since 2010-02-25)

7

Saving the Dataflow updates the code stored in the repository. Something was goofed up and saving a new version of it fixed it.

eganjp :us: (BOB member since 2007-09-12)

8

Very old post. But I still have encountered this today for even at 4.2 version.

When we change the source table on an existing query, for some reason, the old source table definition is still embedded in the query. -thus the error.

On my side, this has been resolved by simply clicking on the FROM tab in the query, then save. This somehow refreshed the source table info in the query

ian_gonzaga :philippines: (BOB member since 2017-07-20)