• Resolved measy

    (@measy)


    Hi Peter,

    in Projects Template – Data Entry it’s possible to check:

    • Visible
    • Read only
    • Less

    In my tests, I need to hide an enum item, defaulting it to one of the predefined values.

    If I check Read only AND use the “Default value” column to hold one of the desired values in the enum set, the enum itself remains selectable (I expected to be grayed out);

    If I check Read only AND un-check Visible AND AND still use the “Default value” as above, the system does not record any value in the underlying db table.

    Thanks in advance for your reply.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Kim L

    (@kimmyx)

    Hi @measy,

    Thanks for letting us know!

    Case 1: The field isn’t greyed out indeed. I’ll raise this with Peter. ??</img>

    No worries for now as even if you add a different value to this field, it will still record the default value you set on the template.

    Please see this demo: https://share.getcloudapp.com/RBuBB0ge

    Case 2: I’ve tested this but the value I set was still recorded.

    Demo here: https://share.getcloudapp.com/xQuOOvBg

    May we know what plugin version you’re using?

    Looking forward to your response!

    • This reply was modified 1 year, 10 months ago by Kim L.
    Thread Starter measy

    (@measy)

    Hi Kim,

    thanks for your kind reply.

    Case 1:

    ok for the non-greyed out Peter’s call to action ??

    I confirm the behaviour described in my previous email (nothing stored if the item is defaulted BUT hidden.

    Would you please re-test by using:

    enum item type (values ‘1’,’2′,’3′);

    defaulting in the template data entry tab to ‘2’ (example)

    hide the field

    then transact a new record

    check the table to see what the (hidden) enum field value is?

    Case 2:

    the version I’m using is 5.2.11

    Best regards.

    Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    Hi Marco,

    I added read-only support to inserts. It will be available with the next update, probably next week.

    For non-required fields this works quite straight forward: the user cannot edit the field. If you set a required field to read-only, the field will still be editable during insert. Otherwise you would not be able to add a row. Only if a default value is defined for a required field, the field will not be editable during insert.

    This should cover most situations, except entering a required field during insert with a default value. This would require a modification to our data model which I like to postpone. If you need this very urgently, it can be done with javascript. Not so beautiful, but very effective. ??

    Thanks for your contribution ??</img>
    Peter

    Thread Starter measy

    (@measy)

    Hi Peter.

    Thank you for your reply: effective and timely, as usual!

    I’m looking forward the new WPDA release, because Yes! the new feature you described is mainly what’s required in my case (the last part being… “wait-able” ??

    Cheers,

    M.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Projects Template – Data Entry’ is closed to new replies.