Kasey

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 94 total)
  • Author
    Posts
  • in reply to: The Modern DFFS is finally here! #35960
    Kasey
    Participant

    Unfortunately I don’t have O365 yet but really looking forward to testing this out soon. It would be very cool if those of you already testing could share screenshots of some of your newly created forms so folks can see what is possible compared to out of the box or very complicated PowerApps solutions. Thanks as always Alex!!

    in reply to: Custom Scripting #35625
    Kasey
    Participant

    Thank you Sir. That is what I understood from a previous email but wanted to confirm.

    in reply to: Custom Scripting #35621
    Kasey
    Participant

    To be clear. You are working on an install and usage package that does NOT require custom scripting to be enabled, correct?

    in reply to: Check Out Functionality #29948
    Kasey
    Participant

    No console errors but it only happens when the form is in dialog mode. When it in full page mode and you click cancel it directs you to display form and when you close that it is no longer checked out. But in modal when you click cancel the modal closes and it is still checked out.

    in reply to: Tab Change Event #29799
    Kasey
    Participant

    I’m all set. Just used good old jquery .click function.

    in reply to: People Fields Read Only Issue #29646
    Kasey
    Participant

    You were right. It happens even when DFFS is not installed. Very strange. I’ve never seen this behavior before. I tried in UAT where Minimal Download Strategy was deactivated and on Production where it was Active. Both had the same behavior.

    in reply to: People Fields Read Only Issue #29626
    Kasey
    Participant

    I verified I don’t have any rules or custom JS that make ANY changes to the people picker fields. I also don’t have those fields in any of the tabs within the forms. Only the {peoplePickerField} in tab row objects. The scenario I had was I had a number field showing as percent that had min and max values in the list settings/field settings. When a user input something out of range and tried to save the form would reload to tell them they had to update the fields to be in range to save. When the form reloaded to tell them that all of the people picker fields were cleared so when they fixed their validation and saved the people picker values were empty. I confirmed that the values were still there after the first save attempt and form reload but empty after the fixed values and subsequent save. Hope that helps. To work around the issue I used custom js to set the attributes of the fields that needed min/max to be number with min and max attributes then added a custom function for on change of the fields to set the value to the min if less than min and to the max value if greater than the max.

    in reply to: People Fields Read Only Issue #29609
    Kasey
    Participant

    This seems like something you will want to take a look at. I will add a custom function to take care of it but the main issue is that when a list field validation fails and the form is reloaded to correct it DFFS loses all people picker field values. I’m sure others have experienced this as well. Definitely not ideal.

    in reply to: People Fields Read Only Issue #29603
    Kasey
    Participant

    I’ve finally identified the root cause. There are number fields with min/max values in the list settings. If a user loads the form the people picker values are there initially. If they enter a value out of range and try to save SharePoint stops the save and returns the user back to the form to fix the min/max out of range values. At that point the people picker values have been wiped out. So if they fix their out of range values and save we lose the people picker values. Until you are able to identify an issue with DFFS re-loading when list field validations fail and can come up with a fix I’ll remove the list field level validations in the list settings and add them to custom JS.

    in reply to: People Fields Read Only Issue #29599
    Kasey
    Participant

    Alex,

    To avoid loosing People Picker fields I removed all people picker fields from all of my tabs and where I need to show them I use table rows with {peoplePicker} to display the name. Intermittently the values are still being cleared. I suspect a timing issue. I was under the impression that if I didn’t include the actual field on any of the tabs it would resolve my issue but it hasn’t. Any ideas how I can eliminate losing my values? Version: 4.4.30

    in reply to: spjs-lookup with datasource #29462
    Kasey
    Participant

    I did look at it but wasn’t sure if I could or how to use it to sort on a different field within the lookup list. Due to the nature of the lookup list I have to be able to define the order for each specific option.

    in reply to: spjs-lookup with datasource #29458
    Kasey
    Participant

    Tried that first but I have no way to order by my “SortOrder” column. I have some field values that start with numbers and some that dont so I can’t use the alpha sort on the option 🙁

    in reply to: Date Format #29449
    Kasey
    Participant

    Just following up to see if it is possible in vlookup special configuration to format a date in 12 hour format?

    in reply to: tabFormValidation #29447
    Kasey
    Participant

    Thank you! This is exactly what I was after. Just FYI, what I have now is a form where no fields are required but a ready flag is not editable until a specific list of fields have been answered. With this solution I created a button to check which fields haven’t been answered yet and show it in your banner. Kind of an on the fly user enabled field validator. Thanks again!

    in reply to: People Fields Read Only Issue #29405
    Kasey
    Participant

    The label is still there. Thank you for reminding me about the delay. I totally forgot about that.

Viewing 15 posts - 1 through 15 (of 94 total)