There was a problem rendering a component of type skuidpage: jSignature is unable to find import plu

Eulogio, it might be helpful for the community to post this on the original thread here so that the original developer of that solution (Peter) as well as everyone else who has contributed to it can see your issue.

I would also suggest posting the full javascript for each of the in-line signature components. If one of the signature components is rendering, but not the other it’s likely something with the JS. Each signature component has a unique id associated with it, right?

Lastly, are you running in Lightning or SF Classic? Lightning requires page support files for any in-line resources: https://docs.skuid.com/latest/en/skuid/deploy/salesforce/lightning/index.html?highlight=lockerservic…

Hi Conlan,

Thanks for the reply, wasn’t sure if this issue was necessarily involved with the original thread aside from using jSignature.

The javascript I posted above is pretty much exactly what is being used for both components. Only difference are some model operations that are being done, but that’s not really relevant to the issue.

I’m also running SF Classic. Again, these signature components were working fine until the Milau update, so this makes me suspect that there was an update to the way resources are being loaded and that’s causing this issue.

Hope this info helps!


Thanks!
Eulogio

Eulogio,

Maybe try regenerating the page support file:  Page Builder->More Page Actions
->Generate Support File.  I think the Millau update handles this for you, but it doesn’t hurt to see if it fixes your issue.

What is your setup on the page?  Are you using 2 Inline Components?  Do they have different Id’s?

Thanks,

Bill

Eulogio,

I just tried the sample page from the original posting in my Developer org (on Skuid 11.1.11). I added 2 inline components (signature blocks). It seems to be working. I have attached it here. It does require a static resource to the ‘no conflict’ version of jSignature (jSignature.min.noconflict.js).

Maybe there is something in your XML that is causing an issue? Did you copy your xml to create the second inline component? Maybe re-add the component using the page builder.

I have seen instances where I have copied xml to add a component on a page and inadvertently typed an extra character. After upgrading, this character caused problems until it was found or we rebuilt the component.

Thanks,

Bill

     </fields>
     <conditions>
        <condition type="param" value="id" field="Id" operator="=" enclosevalueinquotes="true" novaluebehavior="noquery"/>
     </conditions>
  <actions/>

var element = arguments[0],
$ = skuid.$;

$(document).ready(function() {
// init signature canvas
element.jSignature();
element.jSignature(“reset”);

// // Get existing signature from text field
// var model = skuid.model.getModel('Signer'),
//     row = model.getFirstRow(),
//     sigField = 'Signature__c', 
//     sigData = model.getFieldValue(row,sigField);
// if(sigData !== null ) {     // read back Signature data
//     element.jSignature("setData", "data:" + sigData);
// }

})
var params = arguments[0],
$ = skuid.$;

var model = skuid.model.getModel(‘Signer’),
row = model.getFirstRow(),
sigField = ‘Signature__c’;

// get signature from id
var sig = $(“#idSign”);
var sigData = sig.jSignature(“getData”, “base30”);

// update signature text field SF and save
model.updateRow(row,sigField,sigData[0] + ‘,’ + sigData[1]);
model.save();
var params = arguments[0],
$ = skuid.$;

// get signature canvas and reset
var sig = $(“#idSign”);
sig.jSignature(“reset”);

// get signature field, set to null and save model
// var model = skuid.model.getModel(‘Signer’);
// var row = model.getFirstRow();
// var sigField = ‘Signature__c’;
// model.updateRow(row,sigField,null);
// model.save();

Thanks for the reply Bill! I followed your suggestions but didn’t really find anything useful. However, I realized that I was focusing on the javascript for the unrendered component instead of looking at the javascript for the rendered one. I had a condition for an undefined variable when I should’ve been checking for null instead.

I think this had to do with a recent Skuid update: https://docs.skuid.com/v11.0.2/en/release-notes.html#undefined-vs-null-more-friendly-for-old-code

I updated my code and voila it works! I’ll need to make sure to review any other apps that could be affected by this.

Thanks again Bill! Hope folks find this thread helpful 🙂