Dirk Loehn

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • in reply to: Multilingual Cascading Dropdowns #12844
    Dirk Loehn
    Participant

    We have managed to display translated texts for choice fields in all forms Newform, DispForm and EditForm using your localization script (https://spjsblog.com/2013/02/07/translate-choice-column-values-in-newform-dispform-and-editform/) within the custom JS, and leave the default language in list views, which was acceptable for clients.
    E.g. var translationSettings = {“cmTermExtension”:
    {“None”:{“1031″:”Kein”,”default”:”None”},
    {1 Year”:{“1031″:”1 Jahr”,”default”:”1 Year”},
    “2 Years”:{“1031″:”2 Jahre”,”default”:”2 Years”},…

    Since the only purpose of the list is to act as a lookup list for DFFS Cascading Dropdowns, there would be no need to support a localized list view for the lookup list itself. Being able to select a localized value and then store the default language in the target field could be sufficient.

    It’s really sad that SharePoint’s localization features are far from perfect, but this scenario would help in all cases where end users expect to see a fully localized form to add data, and where people working with the data would only work in one default language (which is true in our case).

    So I don’t know if this request is common enough to be useful for others too, but if it is really easy to support international JSON strings, we could definitely use it.

    PS: The only real solution to fully localize “choice fields” that we came up with, was to use a multilingual managed metadata field. Being able to use a localized taxonomy in DFFS is maybe worth a thought, but all we can tell is that handling of managed metadata fields is quite complex.

    So let me know your thoughts.

    Thanks a lot

    Dirk

    in reply to: Filter results – Autocomplete #11700
    Dirk Loehn
    Participant

    Hello Alex, we downloaded and tested the updated version, and it works like a charm. Thanks a lot!!!

    Dirk

    in reply to: Filter results – Autocomplete #11650
    Dirk Loehn
    Participant

    Looking forward to testing it. I guess this is really helpful for anyone in Need for a dynamic lookup list, e.g. only looking up projects that are currently active, or looking up vendors marked as approved etc.
    Thanks!!!

    Dirk

    in reply to: Filter results – Autocomplete #11464
    Dirk Loehn
    Participant

    Hello Alexander, could you see adding this to the Autocomplete solution any time soon?
    That is, beeing able to set a (filtered) list view as the base for an autocomplete search?

    spjs.ac.textField({
    “applyTo”: “cmPartner”,
    “helpText”: “Vertragspartner auswählen…”,
    “listGuid”: “FB46E97C-CAB4-4537-A566-4DBE0FD866E3”,
    “viewGuid”: “…”, ???

    Alternatively, would it be possible to add a function call to do a custom check of a list entry before it is added to the selection?

    spjs.ac.textField({
    “applyTo”: “cmPartner”,
    “helpText”: “Vertragspartner auswählen…”,
    “listGuid”: “FB46E97C-CAB4-4537-A566-4DBE0FD866E3”,
    “validationCallbackFunction”: “…..”,

    in reply to: DFFS Tooltip not showing with jquery UI datepicker #11174
    Dirk Loehn
    Participant

    Hi Alexander, the problem has been located, it is between my 2 ears 🙂

    I have used a line to hide the default datepicker Image
    $(“#dffs_cmDateEnd”).find(“img”).hide();

    this – as I now understand – also removed the tooltip image. Now I’m using

    $(“#dffs_cmDateEnd”).find(“img[id*=DateTimeFieldDateDatePickerImage]”).hide();

    So sorry for you having to look into this, and thanks for the support.

    in reply to: Allo custom value in autocomplete text box #10335
    Dirk Loehn
    Participant

    Wonderful!

    works like a charm – Thanks

    in reply to: Allo custom value in autocomplete text box #10331
    Dirk Loehn
    Participant

    Works great with adding a new entry, thanks a lot!!!

    One problem still is with localization.
    E.g. if we set translated attributes like
    if (lcid == 1031){
    // GERMAN
    spjs.ac.text = {“noItems”:”Keinen passenden Eintrag gefunden”, “noValidItems”:”Keinen gültigen Eintrag gefunden”,
    “invalid”:”Auswahl ist ungültig”,
    “moreItemsLabel”:”Es werden die ersten {0} Einträge angezeigt”,
    “moreItemsMouseover”:”Geben Sie weitere Zeichen ein, um die Auswahl einzugrenzen”,
    “searching”:”Suche nach: ”
    };

    then entering an entry with no Match will result in deleting the entry.
    We have used the setting:
    “allowAddNew”:true, // New in v1.4
    “isLookupInSelf”:false, // New in v1.4

    Apart form this its working great!!!

    in reply to: Document sets? #10098
    Dirk Loehn
    Participant

    Hi Alexander, great this works in Beta4 in general.

    One issue occurs when you create a new document set. Instead of NewForm.aspx, the file /_layouts/15/NewDocSet.aspx is called, and DFFS Reports “DFFS functionality will not be applied because you are attempting to load a non-existing list item (missing ID in the URL).”

    Any idea?

    in reply to: Document sets? #10035
    Dirk Loehn
    Participant

    Hi Alexander, we encountered the same Problem

    We would like to use dffs with document sets – without success so far.
    document sets behave somewhat like folders in a document library, but with added metadata.
    DFFS Setup works, we can configure the tabs, but they are not displayed.

    Dffs works great on same website with a standard document library
    I’m using Dynamic Forms for SharePoint DFFS Backend v4.360|CSS version: 4.10 / |spjs-utility version: 1.257

    Thanks for looking into this – Dirk

Viewing 9 posts - 1 through 9 (of 9 total)