Hopefully, you would have already figured out how to delete the user data from here, but if not,
it's very, very simple and straightforward.
Guys, I mean, the way which I can do the delete operation is I mean, I can do it in many different
ways.
But the easiest way is you can directly parse the export of that particular user and then you can delete
it.
Does that the XPath should be even more dynamic than what it is at the moment.
So, for example, if I want to delete this user, its title to reverse this guy over here.
So this is the test user we have.
And if I want to perform a delete operation, all I can do is I can just do a download a daughter and
then I can search for that as as delete.
You can see that it is not going to show us exactly which you are talking about.
And if I just do a dollar X off the double slash of TRD of text, it is not going to work.
We somehow need to put in normalize space to make that operation working as expected.
So you can see that this is the normalized space which I'm talking about.
So I can just go over here and then instead of DTD, I can just paste this guy like normal space and
you can see that I get the DVD's for that.
But the problem is it's going to give us all the DVDs like all these.
That coming up over here.
Right.
But I need to delete exactly for this particular user, that test user.
So in order to do the exact delete operation for that user, we can do it either by identifying that
particular user, the test user, and then perform the operation.
So, uh, so what I really mean in here is I can just do a.
Operation, something like this, as you can see, what I did is to normalize space dot just auto user
this guy and go to the patent office role so that I can get the role, this role, and then do a normalized
space and then perform a delete operation.
So you can see that I find exactly that same delete operation over there.
So this way I could be able to perform a delicate operation instead of having this operation, which
is not going to work basically.
So I can just replace this to this guy and probably I'm going to use a string interpolation this time.
So I'm just going to use like that.
And instead of the disk user, which I time passing hardcoded because tomorrow the data might change
and we're not going to use the same test user, which is also not correct.
So I'm just going to use this guy and I'm going to say DataDot user dot name something like this and
then perform a delicate operation.
So this way it is going to perform a delicate operation for me, which is going to be really, really
cool as well.
So I'm just going to save this.
And now if I try to run that, but before running it, I'm just going to really delete this user so
that we don't really have this users.
And this other user is also unnecessarily making the data more rubbish.
So I'm just going to delete it now and I'm going to save this.
And if I try to run this test, you could see that the test should run creating a user and you should
also delete the user.
You see that it's performing a delicate operation as well, which is quite good.
So this may be good able to handle the delete operation from a table dynamically.
There is another question students ask me, like, how can I grab all the table rose and table columns
and it's data and store it in a collection or something like that, or maybe even export to a John file
if I want to.
I mean, you can do anything again.
Imagination is the limit for doing everything.
But if you want to really do that, you could also do that as well.
We can talk about that in our next video.
I mean, it's also one of the most simplest thing that you can do.
Just give it a shot by yourself if you're able to do that.
If you couldn't, the solution is already dead in our next lecture.