Losing data/changes made when upgrading platform - updating applications

ismaelDev

Hi staff, I hope you are all fine, Some weeks ago I created some properties relations in "contact" and "ticket" tables, I created some apis so I can get tickets from another helpdesk and then create in REI3, everything working fine, and I upgrade platform so I can update applications, I did it and then I noticed that the data in tables is still there, but the properties and relations inside tables dissapeared, also the apis I created, I know there are CSV for saving data, but when I make changes (adding relations, properties on tables) Which steps may I follow so I can upgrade, update without losing my progress/data, please help me, I had about 8 apis, I'd like to proceed again next time without pain and tears,

Thank you in advance,

Ismael,

gabriel

Did you create your APIs / additional attributes inside the original apps? I am asking because what you describe would be explained this way.

If this is the case, please have a look at the documentation.
Tl;dr: Do not change apps from other people as all your changes will disappear after an upgrade. Make sure to extend apps instead (see docs) to safely add stuff to other peoples apps.

ismaelDev

gabriel Yes, sadly I created the apis inside the original apps (a novice error), I took a look at the documentation and I would like to create a kind of copy of lsw_ticket with another name, so I can make the changes I need, that i would like to know, if can I create a copy of the lsw_ticket with another name? is there a video maybe?

gabriel

You cannot make copies of apps and you do not need to. You build on top of apps, extend them via relationships (1:1 for simply extending existing relations), copy the existing menu (inside your own app) and replace the forms that you want to be different.

In the case of "REI3 Tickets", you really do not want to "fork" this app - ticket systems are complex beasts and require regular updating.

Unfortunately, besides the documentation, there is no tutorial that I am aware of. If you need specific changes, you can always ask. We are regularly updating the app and make changes based on customer requirements as well as general feedback.

lsw-fabian

If you only want to extend API capabilities this could be done pretty quick, because you do not need your own menu & form structures.

Just create a new app, this one needs to build on lsw_ticket. (also on other application if you are referring to other data)
Create your API's in the new app. (If you are using your own backend functions, they can also refer on lsw_ticket functions and structures.)
Create a role which has access to your created APIs and let your role be part of a ticket role (e.g. data_read, data_write or API).
Assign the role to your API user.

There's not much more to do.

Hope this will help you.