Spiky associates a directory to each line of the document table.


In order to have a real rather than virtual directory, you must first configure a root Archive directory which will contain all these directory. See lesson "Configure Archive Directory" for explanations.


Spiky offer the capability to give this directory a name which depends of the content of the table, via a Naming Scheme.


⚠️: Undo management: As Undo / Redo only restore the document state and not the file system state, actions which are modifying the filesystem like renaming files can not be Undone. The renaming operation is thus clearing the Undo stack in order to avoid inconsistencies between the Spiky document and the Archive directory.


Let's start from this default configuration: each directory is named Line_XX where XX is the line identifier.



Let's change the name of the directories from Directory Naming window via:

- Option 1: Toolbar Settings > Directory Naming tab

- Option 2: View > Document Settings > Directory Naming



The default Scheme is composed of 2 tokens:

- A Text token containing a fixed text: "Line_"

- An Identifier token containing the corresponding Line Identifier. This identifier token is mandatory and can not be removed, because each row shall match a single directory.


Let's select the first token by clicking on it (Line_), and press "Delete token" button.



The token is deleted, and the preview of the new scheme updated.

Let's insert a Column token by clicking on the ⊕ button, and select:

- "⊕ Column" to insert a Column token

- "Date" in order to use the content of the Date column

- "Date Format" in order to configure the format of the token date

- And select the desired date format



Our token is ready to be added. Let's press "Add Token"

The preview is updated with the new scheme. Spiky used the content of the Date column to name the directories.

Let's add a "_" text token, an "Invoice Number" Column token and a "_" in order to have a nice scheme:


Our scheme looks good on the Preview. If there is problems like directories already present in the Archive Directory which are conflicting with the new name, press "Show conflict status":


Details of these possible conflicts is explained in the Conflict Management section below.

All seems correct, let's press "Apply new Scheme" to rename the directories, and Execute:

The new scheme is applied. Congratulations !



Press Done. Now, each time a new file is dropped in on a virtual directory, the associated row directory will be created with a name matching this scheme. 


But now, what happen if an existing Invoice Number is modified ? The row directory name will be incorrect !

Spiky handle this scenario, and the row directory name becomes red.

Here 130A has been changed to 130XX, and the name 2020_07_01_130A_1 is out of sync.

Right click on the row directory to rename it correctly to 2020_07_01_130XX_1 



Conflict Management


During the renaming, conflicts may occur:


⁉️ : Existing directory conflict

This icon indicates that you want to rename directory AAAA in BBBB, but that a directory BBBB already exists in the archive directory. In this case, you must solve this conflict yourself before continuing.


In the example below, the real 2020_01_031 directory should be renamed into 2020_01_03_1, but a 2020_01_03_1 directory already exists.


⚠️: Virtual directory conflict

This icon indicates that a virtual directory AAAA will be renamed into BBBB, but that a directory BBBB already exists. 

  • If you do not want to associated the existing BBBB directory to this row, you must manage this conflict manually, by renaming or moving the existing BBBB directory.
  • If you want to associate this row to BBBB, check the box "Accept pairing with existing directories"


In the example below, the virtual directory 2020_01_031 should be renamed into 2020_01_03_1, but a 2020_01_03_1 directory already exists.


: Other files / directories

This icons indicates files or directory which are present in the configured Archive folder, but are not associated to any row and not matching the scheme.





Identifier Matching


Identifier are unique numbers generated by Spiky, and can not be modified.

This may trigger a problem when your scheme match exactly the content of the directory except for the final identifier.


In the example below, 2020-01-04_ is nearly matching 2020-01-04_2



The "Match Identifier" function will force the directory association:


The current association to the row with "2020-01-04_2" will be replaced by an association with "2020-01-04_", leading to the matching of your rows with the existing directories without changing yet the directory names:


You can then let this state if you do not want to rename the directories, or apply the new scheme to have a consistent association.