Question on LGF/LGX - Validation

Question

Hello Experts,
From my understanding, There is LGF (logic file) which is being "compiled" into LGX (logic with all the parameters from database as per SELECT statements). We get LGX file by "Validate and Save" in the application.
Is there any way to automate this?
In the "Admin Task" SSIS  task there is "Validate" option - would it also produce LGX with fresh parameters? Is there is an option when you run logic to use LGF and automatically compile it to LGX with refreshed data?
Please keep in mind that I'm not BPC application user and it is new to me.
Thanks in advance,
Akim

Answer 1

Hi Akim,
I'm not sure why you would need to automate this, as part of an administrative batch process.
I would either validate logic when I'm developing it -- manually, via the admin consol -- or else I'd want it to be validated each time a user runs it, which can be done for batch-mode logic operation by calling the Logic.LGF file (instead of the Logic.LGX file) in the LOGICFILE parameter of the "advanced" script modification in the eData -> Organize Package List setup in Excel.
The second option allows you to take selections from the user's current view, and pass them into the *SELECT statetments and other parts of the logic file, to control the logic execution.
This second option, however, does not actually update the LGX file in the AdminApp\Application directory. The LGF file is validated, and the results are (I assumed) stored somewhere in the logic engine's memory on the app server, but not stored in an LGX file anywhere. (In fact, if you call the LGF file from the package, you can delete the LGX file entirely, with no ill effects.)
Note that this validation-at-run-time option is not available for default logic. This limits the flexibility of what you can do in default logic, compared to batch-mode logic.
But to answer your question directly -- I have seen that "validate logic" admin task, but I've never used it. As a practical matter, the logic should validate exactly the same when it's run as part of this admin package, as when you run it manually from the admin console. So I'm not sure what benefits that admin task would give.
And at least in BPC 5.1, the logic validation itself -- and the error messages that it does and does not provide -- is limited at best. It checks the syntax but it oftens misses critical flaws in the logic, that you'll only discover by either (1.) scanning through the LGX file carefully, or (2.) running the logic and analyzing the debug logs.
Hope that helps,
Tim