#143

Import from Bazis-Mebelshchik (the «3D» section) into iFurn.pro is the most complete way to transfer a project with parts, drillings, edge banding and milling. The import uses a script plugin that is installed into Bazis and exports the project to the iFurn.pro format.

The script comes in two versions — for Bazis 8–10 and for Bazis 11 and 12. During import the system checks the plugin version and, if the export was made with an outdated script, shows a warning with links to the current versions. The import is not interrupted — you decide yourself whether to update the plugin or continue.

What is transferred

  • All parts with exact dimensions (cut and overall) and the label from the Bazis project — a part is easy to match with the original drawing.
  • Materials — unnecessary ones can be turned off at the import stage.
  • Edge banding — per side, with thickness.
  • Drillings — position, depth, diameter, countersink.
  • Grooves and milling — including arc grooves, rabbets and cut-offs; consistent part overall size and contour.
  • Blum/Hettich hardware — drillings for the hardware are transferred (the hardware itself is not added to the project). We keep improving this area.

Common import engine

Bazis import runs on the common engine, like the other sources: a file queue (several exports at once) with per-stage progress, a single «Products» window (selection, renaming, merging sections into whole products) and a 3D preview of the entire assembly before loading it into the order. The plugin's service labels are removed from product names — clean, readable names go into the order.

How to import

  1. Download the script plugin for your Bazis: for Bazis 8–10 or for Bazis 11 and 12. Save the file to the Bazis folder «Scripts → Import/Export». The script can also be downloaded right on the import page; during import the system will warn you if the version is outdated.
  2. In Bazis, open the project, run the script via «Scripts — Import/Export», adjust the parameters if needed (for example, disable drillings for hardware) and export the file.
  3. Return to the import page, upload the file, check the assembly in 3D and the product composition — and create the order.

Only the new script and the JSON format

The former .project export format for Basis is no longer accepted. Upload such a file and the import stops and tells you what to do: download the new exporter script from the import page. It writes JSON.

  • The script is downloaded straight from the import page — the version there is always current.
  • The project is uploaded on a separate import page: in your account or in the CRM for managers.
  • Before it goes into an order you see the assembly in 3D and the list of products.

A file saved by Basis itself rather than by our script will not do either: the system will ask you to convert the project with the script first.

The export dialogue in Basis

The export window has two fields: the file name and the folder. The model directory is filled in by default, but the path can be typed in or picked with a button — the file no longer has to sit next to the model.

The part name format

The header of the import page carries a choice of naming format — six options:

  1. Position (Designation) Name — the default;
  2. Position.Name;
  3. Designation.Name;
  4. Order.Position.Name;
  5. Order.Designation.Name;
  6. Name.

Each option is shown with an example built from one of your own parts. Options whose field is missing in the file — the position or the designation is empty — stand in a separate group and cannot be picked, with a note saying what exactly is missing. If a format you chose earlier becomes unavailable in a new file, the system falls back to the default: otherwise the names would be assembled out of nothing.

When the overall size disagrees with the contour

Sometimes the overall size of a part in the project does not match its contour. Such parts land in the message list together with the numbers: “Side panel — overall 597 / contour 600 → taken 600”.

  • By default the contour is taken, that is the larger size.
  • Below the list there is a switch to the overall size.
  • The choice applies at the next conversion: an already built scene is not rebuilt, the file has to be converted again.
  • A difference counts as a disagreement only above 0.01 mm. Otherwise the list would fill up with parts whose sizes differ by a rounding tail alone.

When the front face is undefined

In Basis itself a part may have no front face set. The plugin exports such a part «as built», with no explicit mark of which face is the front, and during conversion the machining lands where it sits in the 3D model — which may well be the face visible from outside the cabinet.

Such parts are now listed in the messages after conversion: «The front face is undefined in the source BASIS file». Check each of them in the cutting and flip it by hand if needed. The button that detects the front face by the absence of boring finds the obvious cases, but it does not cover everything.