Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Uncaught TypeError : $leadForm.validate is not a function

jewelp4404789
Level 1
Level 1

Hi all,

I am trying to implement third party pixel implementation where I have created a page based rule with 

a) Condition on URL path (for specific URL's , I have to track)

b) Third Party JScript Sequential HTML script.

During testing, I observed that I am getting an error "Uncaught TypeError: $leadForm.validate is not a function" and "Uncaught SyntaxError: Unexpected string"

Could you please provide some background as to why/ in which scenarios do we get such kind of errors?And what is the solution for the same?

For your reference , account name is Pitney bowes 

Web Property : PB - UK

Rule name : 

    
Third Party | UK CIM SCV | Lead conversion

Awaiting response 🙂

Thanks ,

Jewel

1 Accepted Solution
jantzen_belliston-Adobe
Correct answer by
Community Manager
Community Manager

Hi Jewel,

I don't recognize that error. Are you sure that error isn't coming from the third-party script you're deploying? It looks like you are deploying a script with the rule. Have you tried using sequential javascript instead?

I'd suggest we try the following:

  1. Remove the script from the rule by cutting and pasting into a text doc 
  2. Save the rule (no need to approve or publish)
  3. Load your staging environment to see if the error persists
  4. If the error is gone, we know the error is a result of either the script itself or the deployment of the script

I'll wait to hear back on the results of this test.

 

Cheers,
Jantzen

View solution in original post

2 Replies
jantzen_belliston-Adobe
Correct answer by
Community Manager
Community Manager

Hi Jewel,

I don't recognize that error. Are you sure that error isn't coming from the third-party script you're deploying? It looks like you are deploying a script with the rule. Have you tried using sequential javascript instead?

I'd suggest we try the following:

  1. Remove the script from the rule by cutting and pasting into a text doc 
  2. Save the rule (no need to approve or publish)
  3. Load your staging environment to see if the error persists
  4. If the error is gone, we know the error is a result of either the script itself or the deployment of the script

I'll wait to hear back on the results of this test.

 

Cheers,
Jantzen

View solution in original post

jantzen_belliston-Adobe
Community Manager
Community Manager

Hi Jewel,

Any updates on the result of the test?

Cheers,

Jantzen