{"id":13758,"date":"2025-05-08T07:55:15","date_gmt":"2025-05-08T04:55:15","guid":{"rendered":"https:\/\/dhtmlx.com\/blog\/?p=13758"},"modified":"2025-05-08T18:22:51","modified_gmt":"2025-05-08T15:22:51","slug":"backend-data-conversion-integrating-dhtmlx-booking-scheduler","status":"publish","type":"post","link":"https:\/\/dhtmlx.com\/blog\/backend-data-conversion-integrating-dhtmlx-booking-scheduler\/","title":{"rendered":"Backend Data Conversion for Integrating DHTMLX Booking and Scheduler"},"content":{"rendered":"

Not long ago, you learned how to make the DHTMLX Scheduler<\/a> and Booking<\/a> components work smoothly on the frontend<\/a>. Now, it is time to share with you instructions on key points required for integrating these components on the backend, namely, data conversion.<\/p>\n

Conversion Algorithm of Scheduler Events to Booking Events<\/h5>\n

In our demo<\/a>, the integration between these DHTMLX components takes place on the server side. We will go through the data conversion algorithm that allows various types of Scheduler events to be converted into corresponding Booking events (slots). In this blog post, we\u2019ll show how to generate time slots in the booking system from doctors\u2019 schedules using JSON data.<\/p>\n

Before we start exploring the peculiarities of converting scheduler events into Booking events used in our demo, you should get acquainted with the key parameters in both widgets that play an important role in the conversion process of different event types. <\/p>\n

For Scheduler events, you\u2019ll need to know parameters such as duration (start_time<\/strong>, end_time<\/strong>) as well as extra properties<\/a> related to recurring series. As for Booking, you\u2019ll need to get acquainted with id<\/strong>, slotSize<\/strong>, SlotGap<\/strong>, and slots<\/strong> parameters, which are clearly explained in this section<\/a> of the Booking API.<\/p>\n

NOTE:<\/strong> In our scenario, each scheduler event has the doctor_id property that corresponds to the ID of the booking event and points to the ID of a specific doctor in the system.<\/em><\/p>\n

In this blog post, samples for demonstrating the conversion process span from 2025-05-08 to 2027-05-08.<\/p>\n

Conversion of Regular Events<\/h6>\n

A regular (single) event is a basic type of event in DHTMLX Scheduler that occurs once, but may last from one to several days. Let us consider how to convert both variations of regular events into Booking events:<\/p>\n

    \n
  1. Regular One-Day Event<\/strong><\/li>\n<\/ol>\n

    If you need to create a regular one-day event, it is necessary to convert the Scheduler\u2019s start_date<\/strong> and end_date<\/strong> parameters to from<\/strong>, to<\/strong>, and dates<\/strong> parameters of Booking events as shown below:<\/p>\n

    Scheduler event:<\/strong><\/p>\n

    {<\/span>
    \n   "doctor_id"<\/span>:<\/span> 1<\/span>,<\/span>
    \n   "start_date"<\/span>:<\/span> "2025-05-08 02:00:00"<\/span>,<\/span>
    \n   "end_date"<\/span>:<\/span> "2025-05-08 06:00:00"<\/span>
    \n}<\/span><\/div><\/div>\n

    Booking event:<\/strong><\/p>\n

    {<\/span>
    \n   "id"<\/span>:<\/span> 1<\/span>,<\/span>
    \n   "slotSize"<\/span>:<\/span> 20<\/span>,<\/span>
    \n   "slotGap"<\/span>:<\/span> 5<\/span>,<\/span>
    \n   "slots"<\/span>:<\/span> [<\/span>
    \n       {<\/span>
    \n           "from"<\/span>:<\/span> "02:00"<\/span>,<\/span>
    \n           "to"<\/span>:<\/span> "06:00"<\/span>,<\/span>
    \n           "dates"<\/span>:<\/span> [<\/span>1746662400000<\/span>]<\/span> \/\/ 2025-05-08<\/span>
    \n       }<\/span>
    \n   ]<\/span>
    \n}<\/span><\/div><\/div>\n
      \n
    1. Regular Multi-Day Event<\/strong><\/li>\n<\/ol>\n

      Since Booking can only generate slots within one day, you need to split a multi-day event into the required number of slots, one for each day.<\/p>\n

      For instance, let us consider the conversion of a Scheduler event that starts at 8 PM on one day and ends at 4 AM on the next day:<\/p>\n

      Scheduler event:<\/strong><\/p>\n

      {<\/span>
      \n   "doctor_id"<\/span>:<\/span> 1<\/span>,<\/span>
      \n   "start_date"<\/span>:<\/span> "2025-05-08 20:00:00"<\/span>,<\/span>
      \n   "end_date"<\/span>:<\/span> "2025-05-09 04:00:00"<\/span>
      \n}<\/span><\/div><\/div>\n

      Booking event:<\/strong><\/p>\n

      {<\/span>
      \n   "id"<\/span>:<\/span> 1<\/span>,<\/span>
      \n   "slotSize"<\/span>:<\/span> 20<\/span>,<\/span>
      \n   "slotGap"<\/span>:<\/span> 5<\/span>,<\/span>
      \n   "slots"<\/span>:<\/span> [<\/span>
      \n       {<\/span>
      \n           "from"<\/span>:<\/span> "20:00"<\/span>,<\/span>
      \n           "to"<\/span>:<\/span> "24:10"<\/span>,<\/span>
      \n           "dates"<\/span>:<\/span> [<\/span>1746662400000<\/span>]<\/span> \/\/ 2025-05-08<\/span>
      \n       }<\/span>,<\/span>
      \n       {<\/span>
      \n           "from"<\/span>:<\/span> "00:10"<\/span>,<\/span>
      \n           "to"<\/span>:<\/span> "04:00"<\/span>,<\/span>
      \n           "dates"<\/span>:<\/span> [<\/span>1746748800000<\/span>]<\/span> \/\/ 2025-05-09<\/span>
      \n       }<\/span>
      \n   ]<\/span>
      \n}<\/span><\/div><\/div>\n
      Conversion of Recurring Events<\/h6>\n

      Recurring events<\/a> in Scheduler include all parameters of a regular event and several extra parameters:<\/p>\n