For cases when end users want to export the modules for offline reporting repivoting (due to space constraints) we need to offer parity with the Classic UX where there is an option with Code Export.
Workaround means we need to include one extra line item which has to be built for every place required.
Hi @Nikita_S_Gnilozub ,
I think couple of ways you can solve this problem. I personally do not like exporting data from Model for operational reporting prospective. But if that can't be avoided them you can plan to Use a separate model as Reporting Model where u can flattened the data for easy exporting. This Export can happen manually or through integration. Or you can use Cloudwork to export your model data to S3 for manual reports.
I agree - I prefer to save as much screen "real estate" as possible and adding a column for code isn't ideal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.