Thanks @nagarjunav!! Really appreciate your response 🙂I installed the
core.wcm.components.extension-1.0.12.zip on my local (in addition to
Core component 2.12.0) & full-text search works!.I see that it now adds
a "text" property to the CF content node. Were you able to figure out
how this text property is added ?I'd rather add the fix than use the CF
component from extensions package because we have overlaid/extended the
core CF component & updated contentfragment.html as per project
Thanks for the reply Arun.But in my case I have never used the
foundation CF component.The fulltext search works fine when I use Core
CF component ( version 2.3.2) but does not work if I use any higher
version ( I have tried Core CF component version 2.4.0 & 2.12.0)
Issue: Full text search does not return Content Fragment content
embedded within a Page. I am using the core Content Fragment component
to include the content fragment in the page.Environment Details:AEM
version = 6.5.5Core component version = 2.12.0Related issue on this
forum ( Not answered ):
analysis so far:The core Content Fragment component ...
@berliant @nagarjunav Can you please share the fix in case you have
found the root cause?I'm facing Facing the same error & following is my
analysis:AEM version = 6.5.5Core component version = 2.12.0I have
noticed that starting Core component 2.4.0, when Content Fragment
component was moved out of the extensions folder ( i.e. from
adding/editing a CF component ...
I was able to successfully execute the Salesforce.com Export workflow
once I assigned the user "workflow-process-service" permission to Read,
Modify,Create, Delete, etc.. to the /home/users/* pathA new property
called leadID is now added for the exported user and I can see following
success message in AEM
com.adobe.cq.mcm.salesforce.SalesforceExportProcess New Salesforce Lead...
Hi smacdonald2008, @pawan_gupta,Following is the response from Adobe
support when we raised a ticket with for this issue:As per the internal
bug created with the product team, this is a limitation that is being
worked upon on at Internal Jira GRANITE-21310. Once the fix is done it
would be back-ported to the next AEM 6.3 service pack release which can
be tracked using Adobe Experience Manager Help | AEM Maintenance
Releases Roadmap .
Hi All,I have successfully configured salesforce integration in AEM per
this article.However, I am getting the following error when exporting
AEM user as a lead (as mentioned in Integrating with Salesforce
section of the above link):03.08.2018 17:07:43.310 *ERROR* [JobHandler:
com.adobe.cq.mcm.salesforce.SalesforceExportProcess Repository Exception
in Lead Creation Workflow O...
Hi kautuksahni/ navinkaushalThanks for your reply. I modified the
multi-field in the article you mentioned by including the following file
upload widget: But the property cardImageFileRef is being
stored at location "/content/mfCoral63/en/jcr:content/par/touchmulti"
instead of on each of the following
: Can you please elaborate on your previous ...
I am working on a component which requires an image to be uploaded using
fileupload widget inside a coral multi-field Following is the dialog
Issue: When multiple product info is added in the
"Products Tab" of the dialog, the property "productImageFileRef" should
be stored on each of the multi-field nodes. But that is not the case as
you can see below:Note: I have overridden the OOTB