1pux export data will be wrong or old (and uncomplete)

1P_Ben just read your response! Thanks for explaining this :)

THIS IS Happening to me too!!!!!

@Domenico

Oh... if things were only so simple!

Imagine simply trying to make your airplane (you have one, right?) go faster by simply bolting-on more engines. It might seem like a good idea at first, until you realize that the extra air resistance, friction and weight added by the engines, stronger frame and extra fuel requirements defeats the original goal.

The converter is written in an entirely different language, so wouldn't be suited to this. It would either require a complete rewrite (and of course the 1Password folks are fully capable of this on their own; I'd add no value here), or would require a massive add-on wart of code (the runtime environment and libraries) for the sole purpose of doing a CSV export. So, I can safely say this won't happen (nor should it) - too much weight.

Anyway, I hope you have what you need. I'm here if you need more assistance.

Enjoy 1Password!

MrC: I understand it.

The solution would be to integrate the "app" I was talking about into the 1Password App, replacing the existing (very poor) csv export with your "real" one :-)

Best regards,
Domenico

@Domenico

Great!

You can reduce the number of columns by using the --percategory option, as shown in the screenshot above.

In the end, any CSV export will have many columns, since you need one column per 1Password field.

I won't create a binary app, since users would be unable to examine the actual source code and verify no malicious code is involved. I don't want you to trust that I haven't planted some nasty code; I want you, along with others, to be able to verify this.

As to the complexity, I'm very aware of this. I wish I had a good answer.

There have indeed been a few hours involved building this set of tools. :-)

Thanks guys, it worked.

At the end is almost like I wanted it: just ONE ROW per item. The columuns are a lot, but that is normal, as 1P_Ben said, in a database with lots of metadata.

One suggestion, if you allow me: transform all this into a "1-click" 1pux-to-csv converter app...
At the end of the day, your suite (congratulations, by the way, it must have not been easy to create it) does exactly that... but in a way I believe for the common user is a bit too complicated.

Thanks again,
Domenico

@Domenico ,

Provide the path to the originally exported .1pux file, not the export.data file. The converter expects the original 1PUX format, not something you've unzipped.

You can rename the .1pux file from the rather longish 1PasswordExport-xxx-2023-0104-#####.1pux to something simpler such as 1Pexport.1pux. That is easier to type on the command line (in case you are not aware of the shortcuts for providing command line completion or drag-n-drop of files).

Eg:

Thanks a lot guys for your support.

I am using this command line: perl convert.pl -v onepux --to_format csv --ignoretimestamps -o ..\boh.csv ..\export.data

but I get an error message saying "The onepif converter requires a 1PUX file"

Weird, being export.data a 1pux file...

@Domenico

Use the onepux converter. See the Examples mentioned above. They show how to run the conversion. The section 1Password 8 (1PUX to CSV) is the relevant converter in the README.

Please note, the converter suite is not written by 1Password. I'm just a user like you who wrote the set of tools over the years for other users like you and me.

1P_Ben: I am ready to use your converter suite.

I have done all the steps in the readme.html file.

But I don't know which converter I should use.

Would you please tell me which one?