[Alexander Bautz]

This is fixed in v4.352 frontend (September 20, 2015).

Alexander

[Alexander Bautz]

I’m unfortunately not able to reproduce this behavior using the new version. Are you sure you don’ have another rule kicking in and unhiding it somewhere else in your rules?

Alexander

[Alexander Bautz]

Thanks for the feedback, I’ll look into it.

Alexander

[Alexander Bautz]

Hi,
If you search for “calculated” in the search box in the top of the page, you should find a few hits – here is one: https://spjsblog.com/forums/topic/display-a-calculated-column-display-value-in-edit-form/

Alexander

[Alexander Bautz]

Can you test to see if the new version fixes your problem?

Alexander

[Alexander Bautz]

I have digged a bit more and have now fixed it. I’ll post an update during the weekend.

Thanks for you patience.

Alexander

[Alexander Bautz]

Hi,
Are there more than one “line” in the list for each employee?

I’ll consider adding grouping in multiple levels, but this is a bit tricky. You might have to use a custom function to create the output you like. If you have the necessary JavaScript knowledge, you might be able to use the data object returned from vLookup in a custom function? – look here for information: https://spjsblog.com/vlookup-for-sharepoint/vlookup-user-manual/#Accessing_the_vLookup_data_object

Alexander

[Alexander Bautz]

Hi,
You find a trigger named “The form is ready” in the rule, and this can call your custom function in the “Run these functions / trigger these rules” field.

If you use an older version and cannot find this trigger, you can wrap your function call in this function:

function dffs_Ready(){
    // add your code here
}

Hope this helps.

Alexander

[Alexander Bautz]

Hi,
I did some more testing, and it seems there is an issue with using a header in a side-by-side section when you don’t have a heading in the first field in the side-by-side section.

I’ll look into it.

Please note that in general, you should move the hading above the field you plan to use the header in to ensure it is ready when you try to move it to the side-by-side field.

Alexander

[Alexander Bautz]

Thank you for the feedback – I just posted the PROD release – you should check it out!

Best regards,
Alexander

[Alexander Bautz]

Hi,
I did a quick test on the current BETA (where the trigger handling has been reworked) and it looks like it works as expected.

I’m planning to release the prod version next week, and I hope you can test it to see if the rule works in this release.

Alexander

[Alexander Bautz]

Hi,
The code you use targets the <td> and not the <textarea>

Use this format to set any textfield in column 1 to 4 in a site-by-side configuration:

.sbs_tdIndex_1 textarea, .sbs_tdIndex_2 textarea, .sbs_tdIndex_3 textarea, .sbs_tdIndex_4 textarea{
	width:400px !important;
}

Hope this helps,
Alexander

[Alexander Bautz]

Hi,
I did a quick test and could not recreate this issue. Can I see some screenshots of your tab setup?

Alexander

[Alexander Bautz]

Hi,
These additional columns are only available in DispForm (like they are in normal SP forms). You can however use a “Custom JavaScript function” trigger to write your own logic based on a query to find the additional values for the lookup.

Let me know if you need help setting this up.

Alexander

[Alexander Bautz]

Thanks for taking the time to post it.

Alexander

[Author]

Posts