Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

jdonleyNew Participant

Better Processing Rules ManagementNew

Please please PLEASE provide a better interface for managing existing processing rules.   Our options are 1) wholesale wipe and overwrite everything to target rsids2) append individual PRs to target rsids But there is no "overview" to see which PRs are currently where.  So let's say I have 100 rsids, and they are grouped up in different groups.  And I have some "global" PRs common to all of them.  So I add a PR and append to all.  What happens when I need to update later?  My choices are: a) Append a NEW PR that overwrites the previous one.  This is not good, because we're supposed to write PRs to passively pop stuff as a best practice (e.g. "if not set, then set")  b) Go through every rsid individually and update/delete the PR Neither one of these options are good.   Also, currently PRs are not exposed with Rest/Soap APIs so I can't just make my own interface  Ideally I want a PR management interface where it gives an overview of all of the processing rules across all report suites, and which report suites they are associated with, and a button next to each report suite listed for the PR that I can click to remove association with it.  Also a field where I can add one or more.  Or maybe alternatively, each PR would show all of them in a multi-select box (like you have on the current copy interface) that I can simply (de)select which one(s) I want the PR to be active for.   In other words, the overall principle is to only have a single list of PRs and you choose which rsid(s) to associate it with.    That by itself would go a LONG way towards making PR management, well, manageable.   Please?

110723
110723New Participant

Request per hour by API v.14New

Having a request per Hour would optimize a lot the responses because of the large amount of data returned. The functionality is available in v1.3, but it hasn't been provided in the API v1.4. How exist limit of data in return responses, this parameter become very import when is necessary extract informetion that exceed the extraction limits  supported by API.For exemple:While we were trying to test version 1.4 API we faced another error:Scenario tested:API: ReportMethod: QueueEnvironment: San Jose – ProductionRequest:REST 1.4Post URL: https://api.omniture.com/admin/1.4/rest/?method=Report.QueueParameters:{     "reportDescription":    {        "reportSuiteID":"wmbdesktop",        "reportType":"warehouse",        "dateFrom":"2016/11/25 09:00:00",        "dateTo":"2016/11/25 09:59:59",        "Date_Type":"range",        "dateGranularity": "hour",        "source": "warehouse",        "metrics":[{"id": "visits"}],        "elements": [{"id":"evar44"}],        "segment_id":"s2150_5877bf7be4b02fd1c953b4db"    }}Evidence Printscreen:We have requested in this case an specific period of 1 hour (09am to 9:59:59am).Unfortunatelly the output is not attending to this period and show us ‘0’ as hour filter.Even though the period is set as ……the dataset presented is showing us 24 hours (the whole day) of information.  The complete procedure is here:Responses:Beacuse of that, the response of the execution is taking too long and 2 pages of data (not as expected).While trying to actually extract the second page the Responses is presenting ‘forever’ the following message: “sending request for repot.get()...” .No results are returned.Please write back if you have any questions.