[Paul Lynch]

It seems to work fine now, if I change the data type of lookup field from “String” to a “Split options in separate series”. I think on the older version of charts, I tried this but it didnt work, so had dismissed it.

I created a new web part page, which when I matched original configuration of old chart
web part page, and set String for lookup, but this time an error popped up telling me not to use a string, hence it now worked!

Although on both charts, I still cannot get the CAML to populate automatically from drop down. So you’re manual CAML code is helpful thanks.

Thank you for persisting with this.

[Paul Lynch]

Sorry yes I did not add a filter to the view, I did now, just filtered by ID >is greater than 0

I can now see the “Filtered View” as an option. Although when I select it the CAML generated is “undefined” – and an error now pops up when chart loads.

Hope this is progress! (copy pasted errors

Attachments:

1. 

   charthelp4.png
   

2. 

   charthelp5.png
   

[Paul Lynch]

Strange I have no filters I can choose in the optional filter (under filter tab) – see image attached. I created a view in the lookup list to see if that had any effect and it didnt.

Yes both the lists are on the same site.

Attachments:

1. 

   charthelp3.png
   

[Paul Lynch]

Is the lookup single choice or multichoice? – no multiple values selected

Which field is shown in the lookup column (the Title field or another field from the lookup list)? – Title field

Are you using A CAML filter in the Filters tab? – no

(see attached screen shots)

Attachments:

1. 

   charthelp1.png
   

2. 

   charthelp2.png
   

[Paul Lynch]

PS Other info

• I reset the chart, before rebuilding from scratch.
  I’m using a basic table with two fields (Title – String) and (Lookup – String)
  The lookup column is to a list in same site, with 7 different choices.

I CAN get the lookup field to show in my table I switch the Data Type from String to Boolean (Yes/No) – it just shows as a tick for every record!

[Paul Lynch]

Thanks Alex,

I upgraded to version 7.0.0.9 but still have the same issue. Just seems to get stuck on the loading screen when I add a lookup.

[Paul Lynch]

Sorry just realised my mistake – I should have used the very useful “Fields” tab to get my internal field names.

Instead I was using the encoded internal field names taken from URL – once I decoded them it works!

So
%5Fx0031%5F%5Fx002e%5F3%5Fx0020%5FCountry%5Fx0

decoded is;
_x0031__x002e_3_x0020_Country_x0

If anyone ever needs to do this I always find this useful:
https://meyerweb.com/eric/tools/dencoder/

[Paul Lynch]

Thanks for looking Alex – still no idea why it’s not showing in display form.

However I finally got the html/js call to bring them in with your code posted elsewhere here so I am good now thanks.

If anyone else is looking to show 3 calculated columns in Editform. (or has issue showing in Display form see below – my internal fieldname and column names are the same btw)

var qRes = spjs.utility.getItemByID(
	{
		"listName":_spPageContextInfo.pageListId,
		"id":spjs.dffs.data.thisItemID,
		"viewFields":["calccoldate1","calcoldate2","calccoldate3"]
	}
);

$("span.calccoldate1").html(qRes["calccoldate1"].split(";#")[1]);
$("span.calcoldate2").html(qRes["calcoldate2"].split(";#")[1]);
$("span.calccoldate3").html(qRes["calccoldate3"].split(";#")[1]);  

Then in the HTML field added to tab (repeated for each column):

<table style="width: 100%" class="customised1">
	<tr>
		<td class="customisedcss2" style="font-size:10.0pt;font-family:&quot;Segoe UI Semilight&quot;,sans-serif;
mso-fareast-font-family:&quot;Times New Roman&quot;;color:#262626;mso-ansi-language:EN-GB;
mso-fareast-language:EN-GB; width: 87%;">text for the column label
   </td>
<td class="customisedcss3"><span class="calcoldatecss2" /></td>

[Paul Lynch]

Thanks Alex. There are three dates, I just want to show these dates in a display form in a “friendly” format of dd.MMM.yyyy so want to show a calculated column instead of the original field.

PIC 1 – Shows the configuration in form:
1) Original Field
2) Calculated Column (that never shows up)
3) Is HTML in a field column I am trying to use to force it to show up!

PIC 2 – Shows some columns – really just to confirm that the calculated column itself works great.

PIC 3 – Shows the Display Form – notice no calculated column is shown.

I create a HTML field workaround which shows up for one of the dates – “1.15 Start date of the OSQMV:” but not for the others?

PIC 4 – JS of HTML field workaround – first field is ok – but if I just copy line [39] to line [40] and update the reference it doesnt work – keep getting error 80020101 wondering how to add this in, as this might be easier than trying to solve why my calculated column is not showing.

Attachments:

1. 

   PIC1.png
   

2. 

   PIC2.png
   

3. 

   PIC3.png
   

4. 

   PIC5.png
   

[Paul Lynch]

Doh – wrong file sorry – just thought I would wrap this up – now working beautifully again and so is the new BETA version, thanks Alex!

[Paul Lynch]

Dynamic Forms for SharePoint [frontend] v4.4.3.31

[Paul Lynch]

Sorry not done this before, I take a local copy of the DFFS/js/SPJS-vLookup_frontend.js file from my production DFFS.

I drag and drop it into the window of Dans JS tool. (which unpacks it?)

I use the tool to format the JS so it’s beautiful!

Then I scroll down to line 417 and cannot see anything above or below the next 100 line (or more) unless I am blind!

[Paul Lynch]

I appreciate the fix Alex – sorry but please can you tell me which line that code is on?

There are 6057 lines of code

If I copy to notepad ++ cant seem to search and find these exact lines or combination of terms if I split it out.

[Paul Lynch]

In fact yes you’re right – any field that does not have a number to start with (or part of internalfieldname) is shown!

This explains why the “Title” shows – but the field name (non internal) is 1.0 xxxx

[Paul Lynch]

I noticed it is the same on many tabs.

However I think many of these fields do start with a number like 1.0 xxx 1.2 xxx etc..

Here are some examples (with encoded internal field names)

1.10 # Screened-failed:
_x0031__x002e_10_x0020__x0023__x
SPFieldText

1.12 # Early Terminated:
_x0031__x002e_12_x0020__x0023__x
SPFieldText

1.15 Start date of the OSQMV:
_x0031__x002e_17_x0020_End_x0020
SPFieldDateTime

1.16 End date of the OSQMV:
_x0031__x002e_16_x0020_Start_x00
SPFieldDateTime

I use the new cookie function to store which tab it is saved on so if you go back into a form, whichever tab is on does not have these fields.

[Author]

Posts