Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save function doesn't save all row settings. #401

Closed
biiconsulting opened this issue Jan 30, 2017 · 5 comments
Closed

Save function doesn't save all row settings. #401

biiconsulting opened this issue Jan 30, 2017 · 5 comments
Labels

Comments

@biiconsulting
Copy link

I've tried this a couple of times and have been able to recreate the behavior each time - latest editions of Chrome and Edge browsers.

Clicking the save saves all the rows, but not the details about the row. Here's a screen cap of the saved content:

image

After saving with no errors displayed I try to re load the dataset. This is what the loaded dataset looks like:

image

This isn't a huge deal with 8 rows, but I found it after saving one with 35 rows.

Let me know if there's something else I can do to help troubleshoot.

@biiconsulting biiconsulting changed the title Save function doesn't save setting. Save function doesn't save all row settings. Jan 30, 2017
@joelrader
Copy link

Seems like any rows with a "$" cause this issue? Seeing it on 3.2.7. Don't recall seeing it on 3.2.6 though.

@joelrader
Copy link

Also, the number of records to generate is not saved with a data set. Would be a nice to have feature if that's not there.

@benkeen
Copy link
Owner

benkeen commented Aug 25, 2017

Hmm, thanks guys! I'll take a look at this this weekend.

@benkeen benkeen added the Bug label Aug 25, 2017
@benkeen
Copy link
Owner

benkeen commented Sep 9, 2017

Sorry for the wait - my weekends seem to keep filling up! It seems to be an issue with the Personal Number plugin, I'll include a patch for this in the next release (hopefully this weekend).

@benkeen
Copy link
Owner

benkeen commented Sep 12, 2017

Fiddly one! I just committed a fix. This'll be in the next release - may be a day or two until I can get to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants