Skip to content

1CArchiver v1.10 - export 1C(.dt) and plugin Telegram

Latest

Choose a tag to compare

@debalex77 debalex77 released this 10 Oct 05:28
· 4 commits to master since this release

πŸ“„ Changelog

✨ Highlights

  • New plugin Export 1C (.dt): databases are dumped with the 1C platform tools (1cv8.exe DESIGNER /DumpIB)
    • Works for file databases (/F) and server databases (/S cluster\infobase)
    • Configured per database: right click on the database in the table β†’ "Configure .dt export" (1C user, password, optional path to 1cv8.exe; for server databases also the 1C cluster and infobase name)
    • When .dt export is configured, it replaces the native backup (.1CD / .bak): .dt β†’ .7z β†’ .sha256 β†’ Dropbox (optional); the temporary .dt file is removed after archiving
    • The latest installed 1C platform version is detected automatically if no path is set
    • Export errors (exit code and the platform log) are shown in the log and the row is marked ❌; there is no silent fallback
  • New plugin Telegram: after each backup (manual or --autorun) a bot sends a summary (computer, result, start time, duration, βœ”/❌ per database) and the full log as a file
    • Mode always or errors only
    • Test button in the plugin window
    • In --autorun mode the application closes only after the report has been sent (30 s timeout per request)

Bug Fixes

  • Plugin configuration forms: the label of a hidden field is now hidden together with the field (e.g. "User" with Windows authentication for MSSQL)
  • MSSQL: the row is marked ❌ when the .bak file remains locked by SQL Server

Notes

  • The 1C password is passed on the 1cv8.exe command line (the platform offers no other way) and is visible in the process list during the export
  • For server databases the 1cv8.exe version must match the version of the 1C server cluster; set the path explicitly if several platform versions are installed