You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 15, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 15, 2021. It is now read-only.
QueueDataWarehouse doesnt seem to work when elements has multiple classifications #210
I am working on a project to extract bulk data from Adobe using RSiteCatalyst.
My code is as below :
data <-QueueDataWarehouse(my.rsid, start.date, end.date,
metrics, elements,
enqueueOnly = FALSE)
My problem is that "elements", have multiple[read 14] "classifications". However, the output is returning only the "first" classification.Somehow the nesting/recursion doesn't seem to work.
Are you able to do the report you want from the Data Warehouse interface in Adobe Analytics?
Also, what is the actual code that you tried to submit? The snippet you provided is no more than the function stub itself, so it doesn't help determine if this is an RSiteCatalyst issue or a user syntax issue.
=====
Doesn't seem to have a problem with code as it gets information, but only extract the first "classification
variable" is extracted
As you can see that the "prop14" element is internally having other classification variables and the code seems to pick up only the first one which is User email address.
Also,Is there a way to directly feed in "classification" variable in the elements parameter in QueueDatawarehouse function, I tried multiple combinations like prop14.Country, prop14:Country all seem to be in vain
is there any updates for this issue? @ratraspringboard I would like to know if you have found a way to solve you issue, because I also have a familiar one.
I believe QueueDataWarehouse() can accept a classification arg. Needed to do this today and tested an ugly ad-hoc hack, and got results-- need to test and validate, but seems promising.
@randyzwitch : this is probably quite easy for you to implement, but I know you don't really do much with Adobe Analytics these days, so happy to take this on a submit a PR when I've properly tested (would expect a couple weeks). Thoughts?
Activity
randyzwitch commentedon Feb 24, 2017
Are you able to do the report you want from the Data Warehouse interface in Adobe Analytics?
Also, what is the actual code that you tried to submit? The snippet you provided is no more than the function stub itself, so it doesn't help determine if this is an RSiteCatalyst issue or a user syntax issue.
ratraspringboard commentedon Feb 24, 2017
Hi,
Yes, i am able to pull out the report from Adobe Analytics giving the same parameters
The actual code is:
====
suites <- GetReportSuites()
my.rsid <- suites[suites$site_title=="myreport_suite",1]
data <-QueueDataWarehouse(my.rsid, "2016-01-01", "2016-01-02",
"visits", "prop14",
enqueueOnly = FALSE)
=====
Doesn't seem to have a problem with code as it gets information, but only extract the first "classification
variable" is extracted
As you can see that the "prop14" element is internally having other classification variables and the code seems to pick up only the first one which is User email address.
Also,Is there a way to directly feed in "classification" variable in the elements parameter in QueueDatawarehouse function, I tried multiple combinations like prop14.Country, prop14:Country all seem to be in vain
EmilBrink commentedon Dec 7, 2017
Hi Randy, hi Vishal,
is there any updates for this issue? @ratraspringboard I would like to know if you have found a way to solve you issue, because I also have a familiar one.
B/R Emil
ratraspringboard commentedon Dec 7, 2017
drose76 commentedon Feb 8, 2019
Was ever solved by anyone?
slin30 commentedon Oct 29, 2019
I believe
QueueDataWarehouse()can accept aclassificationarg. Needed to do this today and tested an ugly ad-hoc hack, and got results-- need to test and validate, but seems promising.@randyzwitch : this is probably quite easy for you to implement, but I know you don't really do much with Adobe Analytics these days, so happy to take this on a submit a PR when I've properly tested (would expect a couple weeks). Thoughts?
randyzwitch commentedon Oct 29, 2019
@slin30 No, this isn't something I'm going to work on, but I'm happy to review a PR if you submit it
slin30 commentedon Oct 29, 2019
Noted. Will start working on this.