I’m trying to schedule a collection run which will be using a data file.
However, I’m getting the following error:
The data is invalid.
Invalid character in the name property of an item in files.data. Must be alphanumeric or one of !-_.*'()
When I use the same data file via manual run, I’m able to load it.
Hey @maclazaro
Could you share the data file please or a stripped down version that recreates the problem.
Hi @danny-dainton ,
I’ve just been doing that, I have quite a lengthy JSON so I’m trying to isolate bit by bit. It seems to be one of my nested objects as so far, a smaller version can be loaded.
Will update if I’m stuck.
Getting hold of the file would help understand what the problem is you’re facing - Ideally, the same file should work in both the Runner and the Scheduled Runs.
Interested to see what’s going on there so I can raise is with the team.
Just trying to think of what it might be, are there email addresses in the file using @ or one of the keys in the JSON using a special character? 
Within this data file, I’ve enclosed a Swagger to validate responses against.
The file size is less than 1 MB (~350kb), ~12k lines based on the current formatting.
Here is a very shortened and data cleansed version as I thought it’s “$” or “#” which might be causing the error, but the scheduler is able to load this:
[
{
"root": {
"countryCode": "SG",
"scenarios": [
{
"scenarioId": "SCN-001",
"title": "Authentication",
"testRequest": {
"email": "[email protected]",
"id": "{{id}}"
},
"expectedResponseCode": 200,
"responseSchema": {
"scenarioId": "SCN-001",
"title": "Authentication",
"expectedResponseCode": 200,
"responseSchema": {
"$schema": "http://json-schema.org/draft-07/schema",
"$id": "http://example.com/root.json",
"type": "object",
"default": {},
"properties": {
"access_token": {
"type": "string"
}
},
"required": [
"access_token"
]
}
}
},
{
"scenarioId": "SCN-002",
"title": "Login",
"expectedResponseCode": 200,
"responseSchema": "#/components/schemas/ReplyResponseEncapsulation"
}
],
"schemas": {
"Reply": {
"type": "object",
"properties": {
"Count": {
"type": "integer",
"format": "int32"
}
},
"additionalProperties": false,
"required": "Count"
},
"ReplyResponseEncapsulation": {
"type": "object",
"properties": {
"Content": {
"$ref": "#/components/schemas/Reply"
},
"Status": {
"type": [
"string",
"null"
],
"nullable": true
}
},
"additionalProperties": false,
"required": [
"Content",
"Status"
]
}
}
}
}
]
I just need the file you’re using to upload into the Scheduled Run datafile input.
Is it the same as this (minus the parts to make it reduced in size)?
Are you using the datafile to include your schema and use this within the run?
I just need the file you’re using to upload into the Scheduled Run datafile input.
Is it the same as this (minus the parts to make it reduced in size)?
Are you using the datafile to include your schema and use this within the run?
Can you check that the filename only contains those valid characters?
The way that those two feature work or slightly different in the way that they handle datafiles.
Ahh. It’s the spaces in the filename. 
I removed it and it works now. Thanks Danny!
Awesome! I was talking with the team at the same time and got to the bottom of it.
They are going to update the copy on the error message as it was a little confusing as to what the error relates too and even more so when comparing the functionality with the runner.
Glad to see you have that working! 
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.