[brianhoaconnections-com]

Would it be possible to set the csv import to where we could assign whether a mapped input was to be public / private or unlisted?

[Steven Zahm]

@ Brian

Yes. Create a column and name it “Visibility”. Populate the column accordingly using public, private or unlisted. When you map your import select “Visibility” from the drop down.

[brianhoaconnections-com]

Steven,

Great tip, but is there a way to do it on a micro level? Per input?

Here is my dilemma, when I import a directory I want all entries to be public for name and home address, but other inputs set to private unless the user opts to change them to public through link.

Thanks for everything…

[Steven Zahm]

@ Brian

Ahh, sorry, no, not at the micro level. Everything defaults to public. I’ve added it to my feature request list though.

[brianhoaconnections-com]

Thanks for the speedy reply, and I will hold for a future update.

[Blake Miller]

I know this is resolved, but just wanted to point out that this particular field is CaSe Sensitive. I tried to literally match “Public, Unlisted, Private” just like your system shows in both the admin, and in the Import dialog. But it didn’t work. When I went back and renamed my CSV cells to all lowercase, public, unlisted, private . . it worked fine.

Not sure if you can do anything with that, but it threw me for a loop . . until I found this post.

Blake

[Blake Miller]

I should also have asked … but is the “Listing Type” also case dependent? Individual vs. Organization?

BTW – the sample Connection-CSV-Column-Headers.csv that comes with the download files does NOT have any of these “system” type of headers even shown. I recommend adding them, to at least alert a user that they are possible, since they’re not otherwise discussed in any FAQ or manual (that I found.) I didnt’ even realize it until I started testing, then saw those fields “mappable” so went back and started adding those fields to my CSV database.

I also see you released a complete new Rewrite . . TODAY. I think I’m using 0.9 purchased a fwe weeks ago. Is that worth upgrading too? Does it address any of these issues?

[Steven Zahm]

@ Blake

Yes, the rewrite addresses all these issues. I definitely recommend downloading the update.

In the Tips section of the new instructions I made specific mention of the entry type and visibility column. Those are now case insensitive. At the code level I just convert everything to lowercase. Admittedly, it was pretty dumb of me not to do that in the first place.

One of the new items is a dynamically list of column names for fields in Connections. That way if I add a new field in Connections, I do not need to manually make the change to the CSV Import, so it is a little bit smarter. There are also links to an updated Excel which already has the column headers set. It’s not being created dynamically yet, but it is on the to do list. I also added a link to a text file so the names can be copy/pasted. I think those two assets should be of great help.

Probably the biggest change is the import occurs in chunks of 100 using AJAX rather than attempting to do it all in one dump. Large CSV files would hit server resource limits. My one test CSV file which has over 10,000 rows imports just fine on a shared host with very little in resources without issue. I’m probably going to change the chunk size after more testing to 300 to 500 at a time.

Hope that helps!

[Jeremy S]

Hi Steven,

Is is now possible to map a specific input to be private, unlisted or public? I have a list of 1000 entries and some need to be private while others are public. Is there a column I could add in the CSV file that would allow me to update it’s visibility?

Thanks!
Jeremy

[Steven Zahm]

@ Jeremy

Individual details can not be imported as private, public or unlisted but an entry entry can be. Is that what you’re asking? If it is, add a new column to the CSV file, name it Visibility and map it to Visibility. Hope that helps!

[Author]

Posts