Hide
added a comment - - edited
erver: Windows 2008 R2 64 bit
Client: C#
Confirmed Json string being written with .Save and the long value is correct during the save function.
In read function and also the Admin UI the value of the long field is incorrect. Here is an example:
Document: fbUser_634851623223408516
{
"CreatedTime": "/Date(1349565522340-0700)/",
"TableExpires": "/Date(-62135568000000-0800)/",
"UserId": 634851623223408500,
"UserName": "634851623223408516",
"UserPin": "888",
"recType": "fbUser"
}
UserId should be same as UserName as was confirmed during the .Save function.
Any ideas why the long
[DataMember]
[JsonProperty(PropertyName = "UserId")]
public long UserId { get; set; }
Show
added a comment - - edited erver: Windows 2008 R2 64 bit
Client: C#
Confirmed Json string being written with .Save and the long value is correct during the save function.
In read function and also the Admin UI the value of the long field is incorrect. Here is an example:
Document: fbUser_634851623223408516
{
"CreatedTime": "/Date(1349565522340-0700)/",
"TableExpires": "/Date(-62135568000000-0800)/",
"UserId": 634851623223408500,
"UserName": "634851623223408516",
"UserPin": "888",
"recType": "fbUser"
}
UserId should be same as UserName as was confirmed during the .Save function.
Any ideas why the long
[DataMember]
[JsonProperty(PropertyName = "UserId")]
public long UserId { get; set; }
Client: C#
Confirmed Json string being written with .Save and the long value is correct during the save function.
In read function and also the Admin UI the value of the long field is incorrect. Here is an example:
Document: fbUser_634851623223408516
{
"CreatedTime": "/Date(1349565522340-0700)/",
"TableExpires": "/Date(-62135568000000-0800)/",
"UserId": 634851623223408500,
"UserName": "634851623223408516",
"UserPin": "888",
"recType": "fbUser"
}
UserId should be same as UserName as was confirmed during the .Save function.
Any ideas why the long
[DataMember]
[JsonProperty(PropertyName = "UserId")]
public long UserId { get; set; }