Error while updating external MS_SQL DB

[RocketRod]

No no. Do not just look at these two fields. The full record is being committed so you must check all fields. Rules you have in BO may not be correct. Go through the fields one by one and make sure you know what its value is.

Cheers Rod

[rbross]

OK, I will look at that.
Since it is a BO that points to an external table I do not have any Rules on the BO.

[RocketRod]

Oh. If you have changed an attribute on the external table and not refreshed it within AwareIM then they may be your cause. Changes in external tables need to be refreshed. Check that what it shows in AwareIM actually matches your table definition!

Cheers Rod

[rbross]

I have not changed anything on the external table and nothing on the external table has been changed.
But if something was changed, how do you refresh it, Click Discover Attributes under Persistence/Settings for the BO?

[RocketRod]

Yes.

Cheers Rod

[tford]

As I read the rest of the thread, I was going to suggest what Rod did .. re-discover and try again.

If that does not work, I would create a small test BSV that only connects to the offending table and try a simple search and update. Anything you can do to isolate and make 100% sure what is causing the issue.

[rbross]

I will try that Tom, thx.

[rbross]

No luck, same results with the small test BSV.

[tford]

Sounds like you are going to have to get access to the db to inspect it with Navicat or some other tool.

[RocketRod]

Last thought. I assume that your date field is actually a date field as you are setting it equal to Current_Timestamp not current_date?

Cheers Rod

[BLOMASKY]

When I read the error msg Roger, it looks like you are trying to update a decimal field and it is trying to convert a text (nvarchar) field to decimal and failing (miserably). Since your complete attribute is a char field I would assume that is the issue.

Now, in SQL, there can be triggers (sort of like rules in AwareIM) that will run whenever records are added, deleted or updated, so my guess would be:

1) the database columns have changed, specifically the complete column
2) there is a trigger that is being executed that is causing the problem.

Do you have any way to remotely access the sql DB? I can help with that if you wanna give a call.

Bruce

[rbross]

I was going to reach out to you next Bruce!
The error does sound like that, but I am just trying to update a Chr(1) field with 'Y'.
I will see if I can get access to the SQL DB and view it with SQL Manager. That's when I will call on you to take a look with me.

I was going to try one more thing to see if it made a difference.
I will be in touch.

Thanks.

[RocketRod]

Did you check the date and datetime issue?

Cheers Rod

[BobK]

When you Discover the attributes, did you select 1 attribute to be the primary key?