ASP.NET Dynamic Data

Re: Validating on insert

sjnaughton — Sun, 12 Apr 2009 22:28:02 GMT

Well thats wierd I've use this several time

Re: Validating on insert

sksmum — Sun, 12 Apr 2009 19:08:42 GMT

The Issue is solved

i changed my code from

var result = this.Projects.FirstOrDefault(c => c.ProjectID == instance.ProjectID);
to

var DC = new TMSDataContext();
var result = DC.Projects.FirstOrDefault(c => c.ProjectID == instance.ProjectID);

when i use this the result is always ! null ( why no idea )

when i tested with new project i had used DC and not this that is why it worked when changed to this its not working

Re: Validating on insert

sjnaughton — Sun, 12 Apr 2009 14:45:16 GMT

Thats what Sherlock Holmes would say you can always send my the script for a table that gives you a problem and some sample data just a couple of rows and I'll test it here

Re: Validating on insert

sksmum — Sun, 12 Apr 2009 12:58:07 GMT

I 1st tried with only one table and then created a new Test table and tested it

i do not have any sprocs in database yet

i tried with AdventureWorks , i create a test table, it works fine

i think it must be some database issue

Re: Validating on insert

sjnaughton — Sun, 12 Apr 2009 12:13:39 GMT

Have you tried with just the one table? in your new poroject and no sprocs?

Re: Validating on insert

sksmum — Sun, 12 Apr 2009 11:51:21 GMT

Hi Steve

Thanks

It worked fine with NW (SQL Express)

So i created a new project (DD L2S Asp.net 3.5 SP1 ) for my database (SQL Server 2008 Developer Ed) and selected one table

But still its give me the same error even if i enter a new unique value it shows [INR03 already exists as test3]

i created a new table Test with 2 columns TestID INT ( PK, User Input, Not Null ) TestName ncar(10) (User Input, Not Null )

No luck, same error

Re: Validating on insert

sjnaughton — Sun, 12 Apr 2009 10:52:05 GMT

Hi Sksmum, you sode looks good to my what6 I suspect is you still have the sproc's in place and they are doing the insert otherwise the result would be from the DB. Somthing weired is going on.

What I would do is create a new project, create the model, then add the business logic above and debug it test that result is comming from the DB.

My version with Northwind and Customer works fine. If you are still having issues give it a try with Northwind and post your results here.

Re: Validating on insert

sjnaughton — Sun, 12 Apr 2009 10:33:39 GMT

~~Hi can you post the entire yellow screen error please~~

Du! posted to wrong thread

Re: Validating on insert

sksmum — Sat, 11 Apr 2009 21:37:51 GMT

Hi Steve

I tried the above code to the check duplicate

It throw's error even for new unique entry

and in the error message the result.name shows the value of the current input and not the already existing value

Basically i can't insert a new record

here is my code

public partial class TMSDataContext
{
    partial void InsertProject(Project instance)
    {
        //var DC = new TMSDataContext();
        var result = this.Projects.FirstOrDefault(c => c.ProjectID == instance.ProjectID);

        if (result != null)
        {
            throw new ValidationException(String.Format("{0} already exists as {1}.", instance.ProjectID, result.Name));
        }
        else
        {
            // finally send this to the DB
            this.ExecuteDynamicInsert(instance);
        }
    }
}

Thanks in advance

This is my 1st project in ASP.NET

i am using Dynamic Data L2S

Re: Validating on insert

sjnaughton — Tue, 07 Apr 2009 07:27:11 GMT

OK I forgot that . What you do is unmap them after you have testes that they work adn then call them in place of the ExecuteDynhamicInsert etc. also you need to return the PK if it is DB generated on the insert from your SPROC and set the value in the instance before you exit the partial method.

Re: Validating on insert

mdesoysa — Mon, 06 Apr 2009 23:10:53 GMT

Thanks, I changed the properties of the tables but now I am unable to use a partial class for validation as it says that the member is already defined.

So basically I want to use stored procs for insert/update/delete but prior to this I want to validate as I have been doing before.

Any ideas?

Re: Validating on insert

sjnaughton — Mon, 06 Apr 2009 22:19:00 GMT

That means that the primary output of the sproc does not match the table, but you only need to do this for the select, you can just add the SPROC to the Methods panel and then click the table and use the properties to match the speoc to the relavent CRUD funtion OR right click the table and click Configure behavoir. I you do it this way you can still use ExecuteDynamicInsert etc as L2S will call the relevant SPROC.

Re: Validating on insert

mdesoysa — Mon, 06 Apr 2009 21:32:04 GMT

Hi Sjnaughton,

When I drag the stored procs onto the table in the dbml I get this error: "One or more selected database objects return a schema that does not match the schema of the target class".

In attempt to sot this out myself I have added insert and updates methods to my BLL file and have used the actual stored proc for insert. I am using the same ListDetails template for a few pages so in the DetailsViewItemInserting event I find what table is being shown and then call my insert method for that table. I have the code below - how do I get a ContainerCode instance which is what the user has just entered? right now that line is returning a new instance which is null...

VALIDATION AND INSERT CODE in BLL:

// Method for inserting container code
        public void InsertContainerCode(ContainerCode instance)
        {
            //ContainerCode instance = ContainerCode();
            var Fcc = new ParentFccOnlineNettingDataContext();

            // Check that the following are unique: --------------------------------------------------------------//

            // Container Code
            var container = Fcc.ContainerCodes.FirstOrDefault(c => c.FCCContainerCode == instance.FCCContainerCode);
            //---------------------------------------------------------------------------------------------------//

            // If the container code is unique
            if (container != null)
            {
                throw new ValidationException(String.Format("The Container Code {0} already exists. Please specify a different code.", instance.FCCContainerCode));
            }
            else
            {

                // finally send this to the DB
                int? insertedId = 0;
                Fcc.ContainerCode_Insert(ref insertedId, instance.FCCContainerCode, instance.IsActive);

            }

        }

LISTDETAILS.ASPX.CS:

protected void OnDetailsViewItemInserting(object sender, EventArgs e)
        {
            string tableName = GridDataSource.TableName;

            if (tableName == "ContainerCodes")
            {
                ContainerCode instance = new ContainerCode();
                ContainerCodeBLL container = new ContainerCodeBLL();
                container.InsertContainerCode(instance);
            }
            else if (tableName == "Supplier")
            {
            }
            else if (tableName == "Market")
            {
            }
        }

Appreciate some help.

Re: Validating on insert

sjnaughton — Mon, 06 Apr 2009 09:59:29 GMT

Yes if you map the SPROC's to the correct table (by dragging them to the table int he L2S designer) then you can just call them instead with the relavent values

Or you can bind them to the ExecuteDynamicInsert method in the designet see http://msdn.microsoft.com/en-us/library/bb386946.aspx

Re: Validating on insert

mdesoysa — Mon, 06 Apr 2009 04:57:38 GMT

Hi sjnaughton,

Is there any way of doing the insert without using ExecuteDynamicInsert? becuase I want to make sure that the user connecting to the database only has grant execute on stored procedures for security purposes. So any insert/updates etc are done via stored procs only.

Any ideas?