Hi, The error is caused because the Analyzer Maven Plugin is not finding all the dependencies your bundle will use, specifically: com.day.cq.wcm.api;version=[1.30,1.31). You can read more about this issue here: Adobe Experience Manager Core Components - Build Analyzer Maven Plugin.   The missing dep...

Question: I hope this isn’t off-topic, and I’m fine with an opinion-based answer. I’m curious about the specific duties of an Analytics Developer compared to those of an Analytics Architect. My question arises from the following text: My understanding is that an Adobe Analytics Developer typically ...

@AkshaySwamiii The details for OAuth should be present in the new configuration you created as part of the migration process in the Adobe Developer Console[1]. From there, you can retrieve those values and set up the new IMS configuration.   Once that is done, you need to use this newly created IMS ...

Hi,   Technically, there is no limit due to the architecture of AEMaaCS. AEMaaCS is a SaaS service that scales on demand, and the assets-specific product uses a microservice architecture that allows for the separation and independent handling of services. Therefore, as explained by Digarg, there sho...

Hi, You could use the Assets API - Create folder endpoint, please check here how to use it: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/admin/mac-api-assets#create-a-folder    Hope this helps

Hi,  The errors indicate that full-text queries are traversing too many nodes and there are issues with resolving certain resources and files. This causes the queries to stop and the process to potentially fail. I suggest the following two strategies: - Upgrade the indexes so that the queries can be...

@kaisekarenet the classic UI widget are no longer supported nor recommended, so xtype is no longer a viable solution.

Yup, thanks for the clarification

Oh sorry, i didn't catch that you were using POSTMAN, is there any further info along with the 500 error? 

Hi, You can pass assets through a REST call if that's what you are asking, you need to get the "asset" from your request body and build the uploadFiles array with it, that's it.  Something like this would work:   // req = request // file = is the actual asset passed through a POST call in this case ...