LEX App v2.1.11
Bug fixes
- The XLSX report helpers work on the field you actually hold.
self.report.create_excel_file_from_dfs(...)— the spelling everyone reaches for
first — raised anAttributeErrorinside the worker, and only an unbound call through
the field class worked. Both now reach the same implementation. - A report keeps the file name you gave it. The 300-character limit
XLSXFieldandPDFFieldadvertise had never applied — every plain declaration was 100 — and an
over-length name was not rejected but quietly saved truncated. - A dashboard left idle keeps its session. An ordinary page interaction could kill the
thread that renews the token, and a replacement started only on the next interaction,
so a tab left alone after a click expired. That combination is why it looked
intermittent.
No frontend changes in this release. The interface is unchanged from v2.1.10.
Upgrade note: the 300-character limit now applies, so every application usingXLSXField or PDFField gets one AlterField per report column on its nextmakemigrations — which lex_migrate runs on deploy by default. Do not deploy this
release with --no-makemigrations: Django would believe 300 against a varchar(100)
column, and the silent truncation above becomes a DataError.
