Coded Value appears incorrectly

[GeoffreyWest]

I am using the Public Information Center for an application, where I have set the coded values for my status field as assigned, unassigned, and closed....the application intermittently uses the assigned value when placing a point on the map, while it should remain as unassigned.

The application was working until the feature service was overwritten with the same data architecture...

What might cause this behavior??

function CreateServiceRequest() {
    if (map.getLayer(tempServiceRequestLayerId).graphics.length == 0) {
        ShowSpanErrorMessage("spanServiceErrorMessage", messages.getElementsByTagName("mapLocation")[0].childNodes[0].nodeValue);
        return false;
    }
    if (ValicateRequestData()) {
        ShowLoadingMessage("Creating Service Request...");
        var mapPoint = map.getLayer(tempServiceRequestLayerId).graphics[0].geometry;
        var date = new js.date();
        var serviceRequestAttributes = {
           "Address": dojo.byId('txtCustomerAddress').value.trim(),
            "NAME": dojo.byId('txtName').value.trim(),
            "Assignee": dojo.byId('txtAssignee').value.trim(),
            "PHONE": dojo.byId('txtPhone').value.trim(),
            "EMAIL": dojo.byId('txtMail').value.trim(),
            "STATUS": "UNASSIGNED",
            "REQUESTDATE": date.utcMsFromTimestamp(date.localToUtc(date.localTimestampNow()))
        };

[RobertScheitlin__GISP]

Geofefery,

   is "UNASSIGNED" the code or the description of the coded value domain? You are setting this: "STATUS": "UNASSIGNED", I just want to make sure that "UNASSIGNED" is the code for that domain and not the description.

[GeoffreyWest]

Hi Robert,

I have solved this issue, the coded value is UNASSIGNED, I went back and changed my feature service, and my points rendered correctly.