Esta conversa foi bloqueada devido à inatividade. Crie uma nova publicação.
Nível 1
Nível 2
Faça login na Comunidade
Faça logon para exibir todas as medalhas
Esta conversa foi bloqueada devido à inatividade. Crie uma nova publicação.
Hi
I am using the below link to export AEM users as SF leads.
When I start the OOTB salesforce export workflow, it gives me an error as attached. Any Idea how to solve this issue.
Solucionado! Ir para a Solução.
Visualizações
respostas
Total de curtidas
If your experience is not matching the docs -- you may have encountered a bug. Please log a bug here:
http://helpx.adobe.com/marketing-cloud/experience-manager.html
Visualizações
respostas
Total de curtidas
Hi
After entering the instanceURL (https://ap1.salesforce.com) error has been removed. Now there are no error in logs, but workflow is in STALE stage.
At debug level, i found
01.05.2014 18:20:50.978 *DEBUG* [pool-7-thread-11-null(null)] com.adobe.granite.workflow.core.PayloadMapCache /home/users/geometrixx/carlene.j.avery@mailinator.com/profileis either not existing or does not point to the workflow package lookup path: /etc/workflow/packages
How can i fix this. My configuration showing me "Salesforce configuration is successful.Please apply the configuration to your website You can now add Salesforce to your site".
Thanks
Visualizações
respostas
Total de curtidas
Hi
My Payload is : /etc/workflow/packages/geometrixx-outdoors/aaron.mcdonald@mailinator.com/profile
Now there is noting such item not exist in debug message. But still Lead no getting create inside Salesforce.com
Any idea?
Thanks
Visualizações
respostas
Total de curtidas
If your experience is not matching the docs -- you may have encountered a bug. Please log a bug here:
http://helpx.adobe.com/marketing-cloud/experience-manager.html
Visualizações
respostas
Total de curtidas
Can you plz check the instance URL (host url) that you have provided to resolve first issue is accessible correctly from server where you are running the workflow?
Visualizações
respostas
Total de curtidas
rush_pawan wrote...
Can you plz check the instance URL (host url) that you have provided to resolve first issue is accessible correctly from server where you are running the workflow?
Hi
I am using https://ap1.salesforce.com as instance url & configuration showing me "Salesforce configuration is successful.Please apply the configuration to your website You can now add Salesforce to your site ".
Thanks
Visualizações
respostas
Total de curtidas
Hi Scott,
Is there any update on this, I am getting the same error and I am pretty sure this is bug. Is there any hot fix available for this bug.
Thanks for your help in advance.
Kind Regards
Shehjad
Visualizações
respostas
Total de curtidas
Shehjadkhan wrote...
Hi Scott,
Is there any update on this, I am getting the same error and I am pretty sure this is bug. Is there any hot fix available for this bug.
Thanks for your help in advance.
Kind Regards
Shehjad
Hi Sehjad,
Its not a bug, after some tries i was able to sort that issue. Right now I didn't remember what was the cause but you can follow this blog, may be you can get help from it. http://www.intelligrape.com/blog/integrating-salesforce-with-cq5/
Thanks
Visualizações
respostas
Total de curtidas
Hi Vivek,
Thank you for your reply. I am able to debug and root cause this issue.
When we click on "Connect to Salesforce" button in cloud confifguration AEM calls this js file /libs/mcm/salesforce/widgets/cloudservices-workflow-widgets/js/restAPI.js, which internally calls a servlet
(/libs/mcm/salesforce/customer) inside which POST request are made for getting access_token and refresh token. By following the Adobe documentation my connection was failing everytime and was getting the same error as you got (Host is null). I finally figured out in the restAPI.js file there is code block as shown below. json['refresh_token'] was coming undefined.
if(json['refresh_token'] && json['access_token']){
var accessToken = json["access_token"];
var refreshToken = json["refresh_token"];
var instanceUrl = json["instance_url"];
var id = json["id"];
var issuedat = json["issued_at"];
var scope = json["scope"];
var signature = json["signature"];
To fix this problem while configuring the Salesforce connected App, in the scope you have to requiring refresh_token + full access. Just choosing full_access only does not work.
https://developer.salesforce.com/forums/ForumsMain?id=906F00000008pFZIAY
Please see the attached image.
Thanks!
Shehjad
Visualizações
respostas
Total de curtidas
Visualizações
Curtida
respostas
Visualizações
Curtida
respostas
Visualizações
Curtida
respostas