It's a bug of adobe which starts on 21 january and has been solved on 23 january 

Hi, The segment of container doesn't work from yesterday. Instead of a result of json as usual, the response is an error "500 Internal Server Error"Could anyone help me? "segments": [{            "container": {                "type": "visits",                "operator": "and",                "rules"...

Hi Gigazelle,I want to use warehouse with segment. But neither segment container nor segment id works. Here is my reportDescription.{    "reportDescription": {        "reportSuiteID": "xxxxxx",        "dateFrom": "2015-10-01",        "dateTo": "2015-10-01",        "source": "warehouse",        "elem...

Excuse me, do you have any news?

Hi, Here's the details of the segment(https://api.omniture.com/admin/1.4/rest/?method=ReportSuite.GetSegments). I am not sure what is the parameter suite_enabled, because I can not set it in dashboard 15.Maybe it relates with my problem            {                "id":"s1011_565c65d5e4b000f255c10aa...

Is the segment created with API 1.3 different from the segment created with dashboard version 15? I can find the segment created by API 1.3 on the dashboard 15 but the modification and delete of dashboard have no effect on th segment of API 1.3

I am using the API 1.4. I found I can not find segments with the version 1.3 DataWarehouse.GetSegments. It may explain why the first request returns a segment with name null. But is that means a confliction between version 1.3 and 1.4?         "segments":[            {                "id":"{segmentI...

I have tried with 3 types of segments, but none of them works. There are data in the result but it doesn't consider segment.  Could someone help me?{    "reportDescription": {        "reportSuiteID": "{reportSuiteID}",        "dateFrom": "2015-10-01",        "dateTo": "2015-10-01",        "source": ...