Query about using translateDFSlayouts option.
Hello Everyone,
When I am using the following option in a BWR, I get an "OUTPUT() appears to be context dependent - this may cause a dataset not active error"
#OPTION('translateDFSlayouts',TRUE);
In the output statement I am using the dataset which I am preparing in the BWR. I am writing this dataset to a CSV logical file.
The reason of me using this option is there will be scenarios when the logical files on HPCC would have an updated layout (logical file prepared by a different team) and the code would not have those changes (while I am running the code) while reading the logical file. So to avoid an error while reading logical files in case of layout mismatch, I am using this option.
Is there a specific way of using this option ? Should I be considering something while using it ?
Thanks and regards,
Akhilesh Badhri.
When I am using the following option in a BWR, I get an "OUTPUT() appears to be context dependent - this may cause a dataset not active error"
#OPTION('translateDFSlayouts',TRUE);
In the output statement I am using the dataset which I am preparing in the BWR. I am writing this dataset to a CSV logical file.
The reason of me using this option is there will be scenarios when the logical files on HPCC would have an updated layout (logical file prepared by a different team) and the code would not have those changes (while I am running the code) while reading the logical file. So to avoid an error while reading logical files in case of layout mismatch, I am using this option.
Is there a specific way of using this option ? Should I be considering something while using it ?
Thanks and regards,
Akhilesh Badhri.
- akhileshbadhri
- Posts: 26
- Joined: Thu Sep 22, 2016 12:15 pm
The cause is likely to be only indirectly associated with that #option. It is most likely to be some code that precedes that #option or something related.
It may also depend on which version of the platform you are using (if a bug has been fixed). Probably the best approach is to create a bug report on https://track.hpccsystems.com/ and include an archive of the query that fails.
It may also depend on which version of the platform you are using (if a bug has been fixed). Probably the best approach is to create a bug report on https://track.hpccsystems.com/ and include an archive of the query that fails.
- ghalliday
- Community Advisory Board Member
- Posts: 199
- Joined: Wed May 18, 2011 9:48 am
2 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 2 guests