42
 Followers
136
 Likes

Edit data directly in ViewData editor inside Service Studio

Backend
On our radar

I would be great to be able to edit entity data (in addition to the ViewData functionality) inside Service Studio. 

As far as I know, there is no easy way to manually edit data for testing purposes. 

This is extremely helpful especially when bootstrapping data from Excel

Created on 6 Sep 2018
Comments (76)

Changed the category to Backend


I'm working on a project right now, that was just discussing the requirement for this, so that we could adjust data for the purposes of UAT Testing, when a test fails, to be able to reset the data, and try the test again.  It would also be very handy to look at the data before and after testing, to see what changed.

A basic SQL editor is also nice to have (for simple CRUD operations). The ViewData functionality is great, but sometimes you need to just write and execute a quick SQL command.


  

Merged this idea with 'Run Server Action to update records from some entity directly in Service Studio for dev environment' (created on 14 Nov 2018 17:37:46 by Raphael Ranieri)

Sometimes we have to change some data to test something or because they are inconsistent due any wrong development.


For change that if the table do not have a detail screen we have to create a logic in a timer and execute it, or use a advanced query using commit in the end, which is not very known.


The suggestion is to run a single action directly from service studio with some logic to update these records or do whatever you want, without the need to create a timer or a screen to do that!

Or if not possible to run an action, some way to change the data easily in service studio.
Just for dev environments! 



This comment was:
- originally posted on idea 'Run Server Action to update records from some entity directly in Service Studio for dev environment' (created on 14 Nov 2018 by Raphael Ranieri)
- merged to idea 'Data Editor in Service Studio' on 31 Dec 2018 10:18:17 by Vasco Pessanha

Usefull!



This comment was:
- originally posted on idea 'Run Server Action to update records from some entity directly in Service Studio for dev environment' (created on 14 Nov 2018 by Raphael Ranieri)
- merged to idea 'Data Editor in Service Studio' on 31 Dec 2018 10:18:17 by Vasco Pessanha

Just letting you change the data in sql grid.



This comment was:
- originally posted on idea 'Run Server Action to update records from some entity directly in Service Studio for dev environment' (created on 14 Nov 2018 by Raphael Ranieri)
- merged to idea 'Data Editor in Service Studio' on 31 Dec 2018 10:18:17 by Vasco Pessanha

Good Suggestion



This comment was:
- originally posted on idea 'Run Server Action to update records from some entity directly in Service Studio for dev environment' (created on 14 Nov 2018 by Raphael Ranieri)
- merged to idea 'Data Editor in Service Studio' on 31 Dec 2018 10:18:17 by Vasco Pessanha
Merged this idea with 'Ability to ADD, EDIT and DELETE data in View Data in Service Studio' (created on 03 Jan 2019 13:52:22 by Sienna)

It would be really handy to be able to add, edit and delete data directly in Service Studio via the View Data for entities.



This comment was:
- originally posted on idea 'Ability to ADD, EDIT and DELETE data in View Data in Service Studio' (created on 03 Jan 2019 by Sienna)
- merged to idea 'Data Editor in Service Studio' on 04 Jan 2019 09:13:22 by Vasco Pessanha

I see some functionality here, but also some danger. For this to happen it would need to be restricted by role/permission and at least it would need to "push" the SQL warnings/validations.



This comment was:
- originally posted on idea 'Ability to ADD, EDIT and DELETE data in View Data in Service Studio' (created on 03 Jan 2019 by Sienna)
- merged to idea 'Data Editor in Service Studio' on 04 Jan 2019 09:13:22 by Vasco Pessanha

Hey Marios,

I just tweaked the title of this idea so that it can be found more easily by other community members.

Hope you don't mind.

Cheers,

Good idea Marios. When I added mine the automated search told me that it had not found any other similar suggestions.

Merged this idea with 'Edit Entity data from service studio' (created on 07 Jan 2019 11:27:07 by Mohamed)

It will be convenient if there is an option available in the service studio to insert/update the entity data from the service studio apart from bootstrapping. 



This comment was:
- originally posted on idea 'Edit Entity data from service studio' (created on 07 Jan 2019 by Mohamed)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 07 Jan 2019 11:28:02 by Vasco Pessanha
Changed the status to
On our radar


Hi Marios,

Your idea is now on our radar! 

Thank you so much,

Ângela

Merged this idea with 'CRUD in Service Studio' (created on 23 Sep 2019 03:19:01 by Roman Fal's)

The idea is application developer can Manipulate data (Create, Update Delete) in Service Studio. so the developer no need to create webscreen to manipulate data. 



This comment was:
- originally posted on idea 'CRUD in Service Studio' (created on 23 Sep 2019 by Roman Fal's)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 23 Sep 2019 10:10:29 by Ângela Dinis

Up to very recently, developers were able to write a 'Commit' statement in order to have changes in the database done without publishing, as such:

Although the 'Test' feature is temporary, and rolls the changes back, because there was a commit statement, these changes would be permanent. Which meant a developer could do hot fixes without publishing. 


This ability was removed, probably as a security measure. 

I understand that this may pose a serious risk in Production Environments, but it was already possible to block the test feature entirely, and thus block the 'Commit' injection with it. So before, we had two choices.


Allow the test feature + Commit ; Don't allow the test feature ( which blocks Commit )


Now we have:


Allow the test feature ( But don't allow a commit ) ; Don't allow the test feature.


If security was the main issue, blocking the Test feature itself should solve it right?

Our alternative is to create a screen, and put the hot fixes on actions. Is there any difference between creating a screen, publishing it, running the action, deleting the screen and publishing again; and Testing a query with commit?


Looking forward to hearing from you.



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

There is another difference. Allow Testing allows to Test. Delete is not as important as testing queries.

BeforeCan Test QueryCan See DataCan Change Data
Allow TestYesYesYes
Don't Allow TestNoNoNo




NowCan Test QueryCan See DataCan Change Data
Allow TestYesYesNo
Don't Allow TestNoNoNo


I understand you miss that feature (I read it in the forum and heard it on the User Group from several people) but there are different issues here.

You may block Test Data to protect client privacy. That's it. There is awareness that data can't be used.


When you do a Commit, there is no registry on OutSystems of how the data disappeared. The query was tested and deleted. It was a mistake? No one saw.

If you are forced to publish a page/action, you leave a trail. There is awareness that a page exists where data can tampered. Not only you think twice before pressing the Run Query, but the page itself can validate what type of query is running.

For me, that page makes as much sense as the custom CRUD actions where you save dates and users automatically, create a log of interactions and validate the data and the operation.

Some businesses may not need it, but it is a best practice.



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

Indeed, a trail of evidence is left when publishing the screen.

 If that is the only thing keeping a Commit instruction from being a feature, perhaps a trail can be added. Whenever you test a query, a log can be created saying user X ran Query: 'XXXXX' at YYYY-MM-DD HH:mm:ss.

I understand the security issue, but hopefully a middle group can be reached where the development team can still manipulate the database without publishing. 



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

Removing it makes sense for a production environment where you need to leave a trail of evidence that you tampered with data, but for a Dev or Tst environment not having this feature is doing more harm than good, I mean how often you need to delete data from a table because you created a bug? or you created a field that was text but you want to convert it to integer now?
Now we have to create a screen, with a button and a screen action just to fix this, or a timer and run it... 



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

Now I miss this feature. I think it’s a very useful in lower environments.



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

+1, OutSystems, please make our work more easy not more difficult. 




This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

+1 for the idea. Good one.



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

Maybe have it only on environments that aren't in production mode.



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

The Forge has this great component SQL Sandbox created by Leonardo Fernandes, that allows you to execute SQL statements directly on the Platform Database. It even allows you to do so on External Databases.

Check it out if you haven’t already!

Regards,

Nordin



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

Changed the category to Aggregates & Queries




This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

Up to very recently, developers were able to write a 'Commit' statement in order to have changes in the database done without publishing, as such:

Although the 'Test' feature is temporary, and rolls the changes back, because there was a commit statement, these changes would be permanent. Which meant a developer could do hot fixes without publishing. 


This ability was removed, probably as a security measure. 

I understand that this may pose a serious risk in Production Environments, but it was already possible to block the test feature entirely, and thus block the 'Commit' injection with it. So before, we had two choices.


Allow the test feature + Commit ; Don't allow the test feature ( which blocks Commit )


Now we have:


Allow the test feature ( But don't allow a commit ) ; Don't allow the test feature.


If security was the main issue, blocking the Test feature itself should solve it right?

Our alternative is to create a screen, and put the hot fixes on actions. Is there any difference between creating a screen, publishing it, running the action, deleting the screen and publishing again; and Testing a query with commit?


Looking forward to hearing from you.



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

There is another difference. Allow Testing allows to Test. Delete is not as important as testing queries.

BeforeCan Test QueryCan See DataCan Change Data
Allow TestYesYesYes
Don't Allow TestNoNoNo




NowCan Test QueryCan See DataCan Change Data
Allow TestYesYesNo
Don't Allow TestNoNoNo


I understand you miss that feature (I read it in the forum and heard it on the User Group from several people) but there are different issues here.

You may block Test Data to protect client privacy. That's it. There is awareness that data can't be used.


When you do a Commit, there is no registry on OutSystems of how the data disappeared. The query was tested and deleted. It was a mistake? No one saw.

If you are forced to publish a page/action, you leave a trail. There is awareness that a page exists where data can tampered. Not only you think twice before pressing the Run Query, but the page itself can validate what type of query is running.

For me, that page makes as much sense as the custom CRUD actions where you save dates and users automatically, create a log of interactions and validate the data and the operation.

Some businesses may not need it, but it is a best practice.



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

Indeed, a trail of evidence is left when publishing the screen.

 If that is the only thing keeping a Commit instruction from being a feature, perhaps a trail can be added. Whenever you test a query, a log can be created saying user X ran Query: 'XXXXX' at YYYY-MM-DD HH:mm:ss.

I understand the security issue, but hopefully a middle group can be reached where the development team can still manipulate the database without publishing. 



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

Removing it makes sense for a production environment where you need to leave a trail of evidence that you tampered with data, but for a Dev or Tst environment not having this feature is doing more harm than good, I mean how often you need to delete data from a table because you created a bug? or you created a field that was text but you want to convert it to integer now?
Now we have to create a screen, with a button and a screen action just to fix this, or a timer and run it... 



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

Now I miss this feature. I think it’s a very useful in lower environments.



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

+1, OutSystems, please make our work more easy not more difficult. 




This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

+1 for the idea. Good one.



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

Maybe have it only on environments that aren't in production mode.



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

The Forge has this great component SQL Sandbox created by Leonardo Fernandes, that allows you to execute SQL statements directly on the Platform Database. It even allows you to do so on External Databases.

Check it out if you haven’t already!

Regards,

Nordin



This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões

Changed the category to Aggregates & Queries




This comment was:
- originally posted on idea 'Allow Developers to commit changes with an Advanced Query, by writing commit.' (created on 05 Dec 2019 by Christian Lopes)
- merged to idea 'Edit data directly in ViewData editor inside Service Studio' on 03 Jul 2020 11:04:00 by Tiago Simões
Merged this idea with 'Provide feature for edit data directly on Entity like SQL table.' (created on 08 Jan 2020 11:35:55 by Manish Kumawat)

Currently if we want entity with data than we need to define table in excel and than we can import it but the fo