The most frequently asked questions about and of Codebots support.
I have an issue with or idea for Codebots, how do I let you know?
If you have any feedback for us, about ideas, problems or bugs, you can submit them to us via the Submit Feedback button in the side menu of any page. Hop over to our Submitting feedback and bugs article for detailed instructions and a walk-through video on how to do this.
You can also email our support team directly at firstname.lastname@example.org with any issues or feedback you have.
When I hit build, I get a validation “something required” message, can I still build?
Yes, you can still build. Ignoring these validation messages has no impact on the working of your app. Validation messages are merely suggestions and are not actually required to build your application; they are more like reminders to inform you of anything you may have missed by mistake.
I want to submit a Bot Update Request, what is the process?
All you need to do is click the “A new version of this bot is available notification”, read through the information on the pop-up and then click “submit” to send us your request. Our support team receives the ticket, and we pass it on to the tech team to begin the process. Once the tech team has updated your bots, you will need to follow the migration steps in order to migrate your application to your new version of the bot. Note the new version of your bot and follow the migration instructions of each of the previous versions in chronological order (including the upgraded version of your bot), in order to migrate your custom code onto the new version. These instructions are sent to you via the support desk email and are easy to follow. You can also find them here:
Springbot Versions Page
C# Versions Page
Remember you can always get in touch with us if you get stuck or have any issues.
I want to submit a Legacy Migration Request, what is the process?
Follow this link to view a video walkthrough on Completing a legacy migration on Codebots.
Legacy Migration process; how you can help us:
In order to start the legacy migration we need a copy of your schema:
If you are coming from a Microsoft SQL Database, you will need to follow the steps in this article, Export Schema using SQL Server Management Studio (SSMS), to export your schema. You will also need to create a blank “new” app which we will use to load your schema onto.
If you are coming from a different database, you will need to run a command to export your schema. Here is an example of a command you can run:
mysqldump -u my_username -p --no-data my_database_name > schema.sql
Last updated: 01 May 2020