Is it bad practice to access viewmodel from view's class?

I am developing an app with.NET MAUI. For the desktop app, I am using each segment of the app for different data and such. I either had to use prism region navigation or try to do it with the built-in MAUI functions. I didn't use Prism, but the way I implemented the app meant that I often had to call viewmodel functions from view's class.

Is this bad? Right now, I can't think of another way, but if it is a critical problem, I will try to find another way before moving forward.

EDITED:

private async void DeleteButtonTapped(object sender, TappedEventArgs e)
{
    if (answer)
    {
        var bindingContext =  BindingContext as AgentDetailsPageViewModel;
        await bindingContext.DeleteFromDatabase();
        var agentsViews = this.Parent as Grid;
        agentsViews.Remove(this);
        var parentBorder = agentsViews.Parent as Border;
        parentBorder.IsVisible = false;
        var parentGrid = parentBorder.Parent as Grid;
        var agentsBorder = parentGrid.Children[0] as Border;
        Grid.SetColumnSpan(agentsBorder, 2);
        var parentBindingContext = parentGrid.BindingContext as AgentsPageViewModel;
        parentBindingContext.Populate();
    }
}

for example the code above is a situation that i am using the viewmodel in view's class. i'm calling the delete database and populate from my viewmodel but i'm not passing any data.

ObservableCollection<string> creditCardEntries = new ObservableCollection<string>();
foreach (var creditCardborderStack in creditCardbordersStack)
{
    var grid = creditCardborderStack.GetChildren<Grid>().FirstOrDefault();
    var entry = grid.GetChildren<Entry>().FirstOrDefault();
    if (entry.Text is not null)
    {
        if (entry.Text.ToCharArray()[4] != '-')
        {
            creditCardEntries.Add(Regex.Replace(entry.Text, @"(\w{4})(\w{4})(\w{4})(\w{4})", @"$1-$2-$3-$4"));
        }
        else
        {
            creditCardEntries.Add(entry.Text);
        }
    }
}
var bindingContext = (AgentAddOrEditPageViewModel)BindingContext;
if (bindingContext.AgentCreditCardNumbers is not null)
{
    bindingContext.AgentCreditCardNumbers.Clear();
}
bindingContext.AgentCreditCardNumbers = creditCardEntries;
if (await bindingContext.AddToDatabase())
{
    CloseViewAfterInsertion();
}

this is another part of my code and i'm very concerned about this part. basically user can insert infinite credit card numbers. I could not figure out a way to bind them to the viewmodel because eveytime a user wants too add a new credit card i create a textbox in the ui and i could not generate the viewmodel property dynamically to bind it to the textbox.

now if you look at my code you can see that i search through the ui the find the textboxes and get their values. i create a string collection and pass the string collection to my viewmodel. after that i get values and i insert them my CreditCard Class and i do the insertion.

I personally think this is not good but i cannot figure out another way so if you guys have suggestion that might salvage this situation i will be very greatfull.

To see if its bad, you would have to share more information with us, maybe an example of how the access looks like, that you think might be bad.

But generally spoken:

In MVVM, the View accesses the ViewModel, and the ViewModel accesses the Model

V -> VM -> M

So no, it is not a bad practice to access the ViewModel from the View for which the ViewModel was made.

but:

The View and the ViewModel usually belong together. And, the ViewModel should contain no real business logic, but only abstracts the things that the (one) View has to display, and delegate functions and manipulations down to the model.

So: If you would access a ViewModel that does not belong to that View, or even use reusable ViewModels as "model-acess-wrappers", because it already has the correct methods you need to manipulate or read the model, then it would be very wrong.