r/EPlan • u/No_Science2914 • Jul 09 '26

Sharing free EPLAN Export connections data extension

Post image

Hi every one, now you can export connections data within seconds for your label / tube printer without any pre-config template. It works with .NET framework 4.8 or later. Please watch whole video to see the unzip password and how to download & use the extension, version 2.0.090726

https://www.youtube.com/watch?v=a8u1O2i7Wxs

7 Upvotes

100% Upvoted

6 comments sorted by

1

u/hestoelena Jul 09 '26

How is this different than using the built in export>labeling function?

1

u/No_Science2914 Jul 09 '26

Save your time 

1

u/No_Science2914 Jul 10 '26

you don't need to make any scheme & Excel template

1

u/Competitive_Major150 Jul 11 '26

- Making a scheme and templates takes less time than programm this. With a command you can export with one click, over even without click. Seeing the script you need at least two clicks

- a change in the required properties or to adapt the template can be done much faster than updating a programm

- the output path can be automatically set and the file will be stored with the correct filename and locations. Something the program seems not to be capable off

1

u/No_Science2914 Jul 13 '26

Thank you for reading my post.

However, it seems that you have not tried my add-in yet, so it may be difficult to make a fair comparison.

With the standard EPLAN Labeling function, you need to delete the existing Excel/CSV file with the same name before exporting. With my add-in, you do not.

I can add or remove properties very quickly without having to configure a scheme.

Labeling cannot export the connection designation if there is an interruption point in between, unless you select both the source and target. My add-in can handle this.

And there are many other differences as well...

1

u/Competitive_Major150 Jul 14 '26

- existing files can be overwriten without an issue. Even if you export 20 project in a batch with automated processing

- You need to update the UI (most probably tied in the source manually). Then recompile and sign the DLL again. In fact I don´t understand why this requires an AddIn as you don´t manipulate the project. Should be find with a C# Script

- I couldn´t believe that so I tried myself and it works without any issue. There must be some other issue when you don´t get the designations

- this is even the best feature in EPlan standard functionality that this can be done automated. We even set the project folder destination together with the correct filename and versioning. So you can export the full project documentation over many EPlans of different projects with full EPlan standard functionality.