ok, as an alternative you can get same info from Dataset detail page , you have an option to configure calendar to different time durations by defalut it shows records ingested in last 7 days.Does that count help you? regards.

Hi You could use query service to write a query which gives you this info - as long as you have a timestamp or date field in that dataset's schema.

Have you taken a look at https://experienceleague.adobe.com/docs/experience-platform/sources/api-tutorials/encrypt-data.html?lang=en#getting-started.?

@Jörg_Hoh thanks for taking time to respond. Yes i am aware that package will have the xml , but would that be helpful when this is done by possibly a script? flow would be something like --- 1. When the script runs, it will go to AEM , get the xml export (in case of vlt) ...commit that into a repos...

that could have been option if I wanted to only download and install ....I also want to commit those nodes(content.xml) to a repo...thats why want to get content xmls and not package.

I want to export (get) content xmls of nodes under one path and have them downloaded to a local folder , with vlt I would have done something like --   vlt --credentials my-creds-username:password export http://author-xxxxx-xxxxx.adobeaemcloud.com/crx /conf/global/settings/dam/cfm/models myproject  ...

HI @kautuk_sahni , Facing a issue while installing workfront connector package in AEM as a Cloud env. Trying to enable workfront enhanced connector for AEM, We are following instructions as stated in documentation here --- https://experienceleague.adobe.com/docs/experience-manager-cloud-service/cont...

# to allow model.json for react/0064 { /type "allow" /path "/content/<myproject>/*" /method "GET" /selectors "model" /extension "json" } pls change project name and rule number *(/0064) accordingly and try

Check webserver and dispatcher logs, you should get an idea where request is getting blocked.Most probably you dont have a rule to allow these at dispatcher filter. 

thanks for your response ,a) - Is not requirement because exposing only CF individually will have no info about its placement on resulting pageb) experience fragments are not meant to be exposed via GraphQL api as far as I know.c) This could have been an option, although graphQL does not work with p...