Import from CSV

Sorry, I understand now. I thought it was a migration.

In your file, you have defined the following fields:
dates; times; title; introtext; datimage; custom1; access; categories
but when I Try to import, doens't work.

These are the required other columns to import events:
id; dates; times; title; introtext; datimage; custom1; access; fulltext; metadata; publish_up; published; categories

I’ve added the following fields: id, fulltext, metadata, publish_up, and published.
The image path in datimage must exist.
publish_up must be a datetime in the past (if you want to see the event as published).

I’ve sent you a test file for import via PM.
It will be good to add locid with your venue id (if you have any venue defined for this event, so, search will work for venue filter).

Please check the test file and let me know if you’re able to import it and see the event in your calendar.

✅ Answer to your question:

Some CSV files include something called a BOM (Byte Order Mark), which helps programs like Excel recognize special characters (like accents or ñ). If the file doesn’t have a BOM, Excel might display strange characters.
However, for web applications or scripts (like in PHP or Python), it’s usually better to use CSV files without BOM to avoid potential issues. JEM does not require a BOM. A standard UTF-8 encoded CSV is sufficient.

📥 Regarding the import process in JEM:

When importing a CSV file, JEM gives you the option to replace events if the ID already exists, or not. By default, this option is set to NO, which means:

If you provide an ID in your CSV that already exists in JEM, JEM will not overwrite it, but instead create a new event and automatically assign the next available ID. You don’t need to manage the IDs manually, JEM takes care of that.

🕒 About publish_up:

To make sure your event is visible after importing, the publish_up field should be set to the current date/time or earlier. If the date is in the future, the event will not appear until that time.

Let me know if you have any issues with the import or want help checking your CSV file.

I've tested various variants several times , you have to pay attention to the date format (JJJJ-MM-TT hh:mm:ss) and save it in standard ANSI instead of UTF-8. Replace if ID exists remains set to "No." Then the import works. Thank you for your help.

Good!!
Join your import.
This case is fixed and closed.