> For the complete documentation index, see [llms.txt](https://jared-gibb.gitbook.io/fullcalendar-plugin-suite/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jared-gibb.gitbook.io/fullcalendar-plugin-suite/elements/calendar/input-fields/required-inputs.md).

# Required Information

## Required Fields

![](/files/-Mi2GupdBMHPNwk0mAeW)

## :format as text delimiter

* Because of how merging lists works (in the codebase) we must take care with what delimiter we use. The delimiter tells the code where to split up the list we are sending. Typically, in JavaScript, a list is created using commas to separate list items, and this works perfect, even when the list item has a comma. BUT, in our case, we are actually tur[ning lists, into strings](https://www.youtube.com/watch?v=jeL5AD2le50) in the Bubble app,[ joining the strings](https://www.youtube.com/watch?v=9Q8BAZffbz8) in the Bubble app, [and then back into lists](https://www.youtube.com/watch?v=HEdikBHsMag) in the plugin. This can create some issues when the titles have commas. 
* In any event, if you have to `:format as text` ***ONE*** of your 'required event input fields' you'll need to do it to ***ALL*** of them 

{% embed url="<https://vimeo.com/570339716>" %}
In this example, a tilde is used as the replacement delimiter. You can use any of your liking. Be sure that the delimiter wont appear in the text you plan to display as event titles.&#x20;
{% endembed %}

## Event Titles

* These can be any text. You may want to keep this concise to keep your calendar looking cleaner and put extra info in the other properties such as Extra Property 1/2.
* ***Notice!*** If your fields might have a comma, you'll need to `:format as text` the list of titles and modify the delimiter as shown in the video below.&#x20;
  * click 'show documentation' below this input to read more about this requirement.&#x20;

![](/files/-MdbwYRId1qIqWVoGWdD)

## Start Times / End Times

* &#x20;**IMPORTANT**  you must format your Event Times using the built in `:format as` and selecting `format type: Simplified extend ISO`

![](/files/-Mdbw7wZBA2wI9wUcS-P)

{% embed url="<https://vimeo.com/570352049>" %}
When you add your event date/time sources, be sure to ':format as' and select 'Simplified extended ISO'
{% endembed %}

## Event ID's&#x20;

* This value should be pulled directly from the event data source. This is how the events are related and identified in the DB. When you want to modify an event, this is how the app tells the DB exactly which entry to modify.

![](/files/-MdbuZN4hNMxX-c6-gGz)

![](/files/-MdbuqfgjES7QMu0DVYn)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://jared-gibb.gitbook.io/fullcalendar-plugin-suite/elements/calendar/input-fields/required-inputs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.