Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
I'm running the Gov Dashboard 2.0.1 and I'm receiving the attached general error.
The script can't find the field SOE_Type when loading from the resident table SOE.
I attached the end of the log.
,KR Koen
2016-04-21 15:12:35: 0903 Expressions:
2016-04-21 15:12:35: 0904 Load
2016-04-21 15:12:35: 0905 ObjectKey,
2016-04-21 15:12:35: 0906 ObjectKey & Definition as ExpressionKey,
2016-04-21 15:12:35: 0907 Label as Expression_Label,
2016-04-21 15:12:35: 0908 Definition as Expression_Definition,
2016-04-21 15:12:35: 0909 SOE_Comment as Expression_Comment
2016-04-21 15:12:35: 0910 resident SOE
2016-04-21 15:12:35: 0911 where SOE_Type ='Expression'
2016-04-21 15:12:35: Error: Field not found - <SOE_Type>
2016-04-21 15:12:35: General Script Error
2016-04-21 15:12:35: Execution Failed
Related questions: Governance 2.0 not loading properly
I made some improvements to the fileScan SUB. Now it already skips the folder before going into the folder, selecting a file and checking for that file if it is part of a folder which should be excluded.
twa
The QVGD_SOE_2.0.1.qvd does indeed only contain the field _concatSOE.
Is there a limit to the number of files/paths in the fileScan SUB?
It seems that the script does not read all the subfolders of my main folder.
Why does the script also checks in the subfolders of folder X, when X is an exclusion parameter?
,KR Koen
I made some improvements to the fileScan SUB. Now it already skips the folder before going into the folder, selecting a file and checking for that file if it is part of a folder which should be excluded.
twa
Will you share?
Hello Tyler,
The original and improved fileScan SUB should be attached to my earlier reply.
I changed
for each fldr in DirList('$(root)'&'\*')
Concatenate (FilePaths)
Load '$(fldr)' as %FilePath, RowNo() as %FilePathNumber autogenerate(1);
CALL fileSearch ('$(fldr)',$(n))
next fldr
to
for each fldr in DirList('$(root)'&'\*')
IF NumExclusions > 0 THEN
set exclusionsFound = 0;
For x = 0 to $(NumExclusions)-1
let exclusionsFound = exclusionsFound + SubStringCount(lower('$(fldr)'),'$(exclusion$(x))');
Next x
IF exclusionsFound > 0 then
let msg = 'The folder $(fldr) has been excluded from this scan due to user defined exclusion parameter.';
TRACE $(msg);
ExcludedFiles:
Load '$(fldr)' as ExcludedFile, $(exclusionsFound) as ExclusionRulesFound Autogenerate 1; // Generate a table of excluded files
ELSE
Concatenate (FilePaths)
Load '$(fldr)' as %FilePath, RowNo() as %FilePathNumber autogenerate(1);
CALL fileSearch ('$(fldr)',$(n))
ENDIF
ENDIF
next fldr
,KR Koen
cheburashka - I used this script in a customer call today and it was much more efficient and appears to fix this customer's issue with having 9 exclusion parameters! Nice work!
One comment, though, you need to add "ENDSUB" to the bottom of your "improved" load script.
I will add this to the improvements list for a future release of the Governance Dashboard. Thanks for contributing!
Hi all - SR2 of Governance Dashboard (2.0.2) has been released which addresses this issue! See
Thanks for the input cheburashka!