included additional test job covering multiple scenarios. Closes #337
Issue
337
Intent
support for multilable and notsored formats
Implementation
Created a calculated FMTROW variable, and used this (plus TYPE and FMTNAME) as the primary key when dealing with format catalogs
A format catalog can contain duplicate rows when working with multilabel data. The order is also important. Therefore the (relative) position of the format (row) entry must be part of the key.
Also added a header to the mp_ds2md() macro when printing to the log (for ease of identification)
Now that START/END are not part of the key, we can support values back up to 32767.
Checks
[x] Code is formatted correctly (sasjs lint).
[x] Any new functionality has been unit tested.
[x] All unit tests are passing (sasjs test).
[x] all.sas has been regenerated (python3 build.py)
included additional test job covering multiple scenarios. Closes #337
Issue
337
Intent
support for multilable and notsored formats
Implementation
Created a calculated FMTROW variable, and used this (plus TYPE and FMTNAME) as the primary key when dealing with format catalogs
A format catalog can contain duplicate rows when working with multilabel data. The order is also important. Therefore the (relative) position of the format (row) entry must be part of the key.
Also added a header to the mp_ds2md() macro when printing to the log (for ease of identification)
Now that START/END are not part of the key, we can support values back up to 32767.
Checks
sasjs lint
).sasjs test
).all.sas
has been regenerated (python3 build.py
)