export master command -d flag file path error #19
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
more info required
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
yulqen/datamaps#19
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When doing the command
datamaps export master [PATH to master] -d [PATH to datamap.csv]get the error:I've kept the actual file path in there so you can see that the file path is being repeated. i.e. has Documents twice.
You only need a dummy master and datamap to check this.
If you put the datamap in another location (Desktop?) and call again, do you get a similar error?
Yes.
CRITICAL - Cannot find C:\Users\Standalone\Documents\datamaps\input\Desktop\datamap_export.csvCan you please email (personal email) me a copy of the current blank_template.xlsm file so I can test with most up to date files? I've probably got one around somewhere on another machine but if you an ping it in an email, that would be great. Ta.
Done and done.
Unable to reproduce.
What is the exact command, Will - particularly what does the path to the datamap file look like in the
-dflag? I've tried both relative and absolute path with no problems. Not tested on Windows.Yes this error was on Windows. However, given you couldn't reproduce did some further testing and got it to work with absolute rather than relative file paths. so
works. But
gets the error as above.
The second example you give (the relative path) wouldn't work unless your
working directory is C:\Users\Standalone. You could use
echo %cd%in the command prompt to check that. Assuming that is the case, I'm not sure what's going on here and would have to do some testing in Windows. But advice for now is use the absolute path.Don't forget your can write your commands into bash scripts if you're doing them
a lot! You don't have to keep typing 'em out...
On 29-04-2021, Will Grant wrote:
--
Matthew Lemon
Email: @.***
Yeap working directory is C:\User\Standalone so weird.
Use absolute paths for now to be safe; leave the issue open, I'll look into
this.