Nextworld help states that flat report execution logic blocks be of type Background Task. However, I’m looking at a report where that logic block is of type Transaction and nothing is preventing or validating against it being of type Transaction. I’m seeing some unusual things and weird behaviors, and want to know if this callout in Nextworld help is a recommendation or requirement. Does anyone know?
This is a best practice recommendation. Since Reports run asynchronously in a batch job, the report logic block will automatically run in the background, regardless of how it is configured.
1 Like
@jeremy.keller does it even make a difference or all works the same under the covers?
@ian.p All the same under the covers in production use cases when a report is run.
The only difference you could notice is when running this logic block during development outside of the reporting framework, such as setting it up as a row action to test if data is being queried/populated correctly. The background task LB would get run as a job, the other types would be run synchronously on the spot.
1 Like