I am trying verify the create user section. I do not see that anything is missing and it keeps giving an error.

I am using a trigger to create a task on an Account record.  The task should be created when a "notice" date on the account equals today's date.  I have the trigger working but every time I edit the account, it creates another task.  I only want one task for when the date criteria is met.  The notice date will change to a future date so the process will start all over once the new notice date equals today.  I read a few of the posts but I am not seeing something that matches what I am trying to do.  I am an admin but working to get more involved with developing. Thanks for any help.

 

1 2 3 4 5 6 7 8 9 10 11 12 13 14

trigger WaiveTaskCreate on Account (after update) {    for (Account acct : Trigger.new){    if(acct.Date_Notice__c==System.Today()){        Task t = new Task();        t.Subject    = 'Subject';        t.OwnerID = acct.OwnerID;        t.Priority   = 'High';        t.Description    = 'Comment';        t.WhatID     = acct.Id;        t.ActivityDate = (acct.Exp_Date__c + 15);        insert t; } } }

 

I am trying verify the create user section. I do not see that anything is missing and it keeps giving an error.

Hi all, 

I have a production salesforce trial account and i'm trying to connect to BO Data Services using data services's adapter.

All the requirement were met (Proxy requirement met ; password =account pass+security token ; Verisign Certificate added ; TSL1.1 and TSL1.2 enabled...etc.)  but i'm still getting the following error when i try to connect DataServices to Salesfoce : 

" ​There was a communication error when talking to Salesforce.com: org.apache.axis2.databinding.ADBException: Unexpected subelement {urn:fault.partner.soap.sforce.com}upgradeURL 1/31/17 4:26:20 PM Thread[Thread-25,5,main] Fault-tolerance-login-failed : There was a communication error when talking to Salesforce.com: org.apache.axis2.databinding.ADBException: Unexpected subelement {urn:fault.partner.soap.sforce.com}upgradeURL "

I tried all the following URLs but i'm still getting the same error: 
https://salesforce.com/services/Soap/u/21.0 (URL by default in Data Services)
https://login.salesforce.com/services/Soap/u/38.0
https://login.salesforce.com/services/Soap/u/21.0 
https://salesforce.com/services/Soap/u/38.0

Do you have any ideas about how to resolve this -i'm stuck with this error for about a week :'( - ?

Many thanks by advance, 
Ezzar



 

I am using a trigger to create a task on an Account record.  The task should be created when a "notice" date on the account equals today's date.  I have the trigger working but every time I edit the account, it creates another task.  I only want one task for when the date criteria is met.  The notice date will change to a future date so the process will start all over once the new notice date equals today.  I read a few of the posts but I am not seeing something that matches what I am trying to do.  I am an admin but working to get more involved with developing. Thanks for any help.

 

1 2 3 4 5 6 7 8 9 10 11 12 13 14

trigger WaiveTaskCreate on Account (after update) {    for (Account acct : Trigger.new){    if(acct.Date_Notice__c==System.Today()){        Task t = new Task();        t.Subject    = 'Subject';        t.OwnerID = acct.OwnerID;        t.Priority   = 'High';        t.Description    = 'Comment';        t.WhatID     = acct.Id;        t.ActivityDate = (acct.Exp_Date__c + 15);        insert t; } } }

 

Hello.

We are unable to authenticate with the SFDC API despite entering the correct username, password and security token. The message returned is:

INVALID_LOGIN: Invalid username, password, security token; or user locked out

This is for a developer account, so we are using the https://na15.salesforce.com/services/Soap/u/19.0 API URL. We have also tried with https://login.salesforce.com/services/Soap/u/19.0 and get the same result.

We have tried with an Administrator account and another API enabled account.

However, we know that the username, password and token are all correct. And we can log into the account through the UI front end, so it does not appear to be locked out.

Can anyone advise what we can try next to authenticate please?!

Many thanks,
Jon