recording app: incorrect message about exceeding 100 lots

[luizaogs]

I think this is a problem but since I still need to test about 500 lot configuration keys I'm not sure, but reporting it before I forget.

I'm testing the auto generation of lots and I just got a message that I have exceeded the max 100 number of lots for a context, though the context clearly only has one lot:

[luizaogs]

Also getting this if I have no lots for a context. The combination of config keys I have currently is nope for auto_generate and free input for input_type:

[luizaogs]

I'm also getting this for units, even if I do not have 100 lots in that unit.

[urapadmin]

that's miserable failure across the board then

[urapadmin]

I think this is a problem but since I still need to test about 500 lot configuration keys I'm not sure, but reporting it before I forget.

I'm testing the auto generation of lots and I just got a message that I have exceeded the max 100 number of lots for a context, though the context clearly only has one lot:

so in this one you had auto_generate "yup" and input_type "auto" and lot_domain "locus"?

[urapadmin]

ja, I can reproduce this one. Good.

[luizaogs]

I basically got the wrong warning for any combination of keys I was using.

[urapadmin]

ja this would have happened more or less as soon as you have an upper limit. Sometimes FileMaker does not take 100 for a number. Why that did not happen to me yesterday I can't tell.

recording 15.14.1

• it should be okay now

[urapadmin]

in this case it also makes sense to work with a lower upper limit, just because I once had the 100 hard coded and we would not catch a left over line with that in if we keep testing with 100.

[luizaogs]

Looks good now, and I tested with max 78 rather than 100 just in case.