[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

[Alexander Bautz]

Hi,
I have changed the trigger handling in the upcoming BETA 3 and I’m afraid I’ll have to ask you to test the trigger in the new BETA.

When it comes to yous show/hide function, you must either use include a <table> tag – or loose the <tr> and <td>. The browser will “fix” the HTML by wrapping it in a <table> tag, but this may end up a bit messy.

I have trimmed down your code a bit:

<div class="InstructionHeadOpened" onclick='$(this).next().toggle();' style='cursor:pointer;'>Show / hide Instructions</div>
<div class="more" style="color:black">
<p>To create a <strong>new</strong> request:</p>
</div>

No need to use the “showHide” function.

PS: You could also use the “Tooltip” tab to have this instructions pop up as a tooltip.

Alexander

[Alexander Bautz]

Thanks, but unfortunately I cannot recreate this. I’m finishing up the last of the fixes for the BETA 3 that I hope to publish during the weekend. I’m afraid I’ll have to ask you to test this version when I get it published.

Best regards,
Alexander

[Alexander Bautz]

Hi,
Try adding a “console.log” like this before the line “$(“span.WeightedDocumentVolume”)…”:

console.log(qRes);

To see the output you must have the developer console open – hit F12 > Console.

Post the output here.

Alexander

[Alexander Bautz]

Thank you for the feedback, are you 100% sure you haven’t loaded DFFS twice in the form?

Do you see any errors in the developer toolbar (hit F12 > Console)?

Best regards,
Alexander

[Alexander Bautz]

Thank you for the beer!

Alexander

[Alexander Bautz]

Try changing the query like the attached image and you should be OK.

Let me know how this works out.

Alexander

Attachments:

1. 

   ProjectLookupImg.png
   

[Alexander Bautz]

Hi,
You find this in the “Tabs” configuration in the DFFS backend – it is named “Add heading or HTML”.

Your text string looks good, but you need to adapt the “query” and the line setting the value in your heading to match the class you used on your <span>

Alexander

[Alexander Bautz]

Hi,
Sorry for the delay.

I cannot see any reason why this should not work. Can you attach a few screenshos of the vLookup configuration for this field? – including a screenshot of the field table for the vLookup (you can expand this above or below the viewfields section) to ensure the FIN is correct for the field you use in the query.

Alexander

[Author]

Posts