Issue while inserting data in third party data source

RE: Issue while inserting data in third party data source

komalc3 — Wed, 09 Aug 2017 08:38:38 GMT

Hi @jamins952

Since in my case, the Id is an auto generated value and not sequence generator so I used the attibutes for GeneratedValue provided by you, but I didn't help me out either.
Thanks!!

RE: Issue while inserting data in third party data source

komalc3 — Wed, 02 Aug 2017 07:10:05 GMT

Hi

There is no mis match between CDT and Table as I mentioned in my query earlier, I can select as well as update the table but cannot insert due tot he ID field.

RE: Issue while inserting data in third party data source

aloks0189 — Tue, 01 Aug 2017 04:29:44 GMT

So, in such case, are you sure about, the changes made in CDT's are reflecting to the DB properly?

RE: Issue while inserting data in third party data source

komalc3 — Tue, 01 Aug 2017 04:18:40 GMT

Hi Alok

I can't drop the tables as the Oracle 12c database is not only hit by Appian but also by other systems.

RE: Issue while inserting data in third party data source

Jasmin — Mon, 31 Jul 2017 10:28:00 GMT

Hi Komal , Can you try below annotations on ID field.
@Id
@SequenceGenerator(name="my_SeqGenerator", sequenceName="DB_Sq_Name")
@GeneratedValue(strategy=GenerationType.SEQUENCE, generator="my_SeqGenerator")
@Column(name="ID", columnDefinition="NUMBER(12,0)")

RE: Issue while inserting data in third party data source

aloks0189 — Mon, 31 Jul 2017 10:16:41 GMT

HI just for confirmation, are you dropping and recreating the tables by publishing the Data Store while modifying the XSD?

RE: Issue while inserting data in third party data source

komalc3 — Mon, 31 Jul 2017 10:15:37 GMT

Ravi Roshan

Thank you for replying!!
As mentioned in my query itself (on top of the query section), the primary key is passed as null through Appian interface thus Write to Data store entity breaks, which is an expected behaviour.
I want to know how does the primary key gets auto generate because in Oracle 12c itself it is handling it via. "GENERATED AS IDENTITY NOT NULL".

RE: Issue while inserting data in third party data source

Ravi Roshan — Mon, 31 Jul 2017 09:14:41 GMT

CREATE TABLE [dbo].[XYZ](
[ID] [int] IDENTITY(1,1) NOT NULL,
CONSTRAINT [PK_XYZ_3214EC2773] PRIMARY KEY CLUSTERED
(
[ID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
)

The second query was, are you providing and value for ID in your PV as " "(Space character) or null?

RE: Issue while inserting data in third party data source

komalc3 — Mon, 31 Jul 2017 07:22:04 GMT

Hi ravir93

Thank you for replying!!

The primary key configurations: are:
"GENERATED AS IDENTITY NOT NULL".
Can you please elaborate the second question that you have asked.

RE: Issue while inserting data in third party data source

Ravi Roshan — Fri, 28 Jul 2017 12:09:36 GMT

Can you share the Primary key configuration from your DB, I suppose there will be some issue. For the other side are you providing any value for ID column?

RE: Issue while inserting data in third party data source

komalc3 — Thu, 27 Jul 2017 03:27:12 GMT

Hi @ravir93

Thank you for replying!!
But this is also not working.

RE: Issue while inserting data in third party data source

Ravi Roshan — Tue, 25 Jul 2017 12:26:34 GMT

Can you please try with this:

<xsd:element name="id" nillable="true" type="xsd:int">
<xsd:annotation>
<xsd:appinfo source="appian.jpa">@Id @Column(name="ID", columnDefinition="int", nullable=false) @GeneratedValue</xsd:appinfo>
</xsd:annotation>
</xsd:element>

And please also check the primary key configuration in table also.

RE: Issue while inserting data in third party data source

aloks0189 — Tue, 25 Jul 2017 12:10:02 GMT

As per my understanding, if that's a Third Party System, then we don't have any control over that system, i mean to say

The Sequence must be created from 3rd party Side, the consumer or the one who is going to consume the service/Client, is no where responsible for configuring sequence over a table.

So while creating the CDT, we just need to mark one Property (like ID) as PK but not Auto generated.

Also, when you want to persist the data into 3rd Party System, the 3rd Party must define some approach, like an API or function etc. through which the Client can pass the remaining column/property values where the id will be generated by help of Sequence or using Sequence with Trigger

RE: Issue while inserting data in third party data source

PhilB — Tue, 25 Jul 2017 06:34:37 GMT

Probably worth a support case then!

RE: Issue while inserting data in third party data source

komalc3 — Tue, 25 Jul 2017 03:09:31 GMT

Hi @phib

Thank you for replying!!
I have tried individually with @GeneratedValue as well as @SequenceGenerator and using them together as well, but the issue still persists.

RE: Issue while inserting data in third party data source

PhilB — Mon, 24 Jul 2017 11:25:23 GMT

I'm guessing you're on Oracle 12c? Have you tried it with the @GeneratedValue annotation but without the @SequenceGenerator annotation? I think IDENTITY means you don't get a sequence name - it's Oracle's equivalent of AUTO_INCREMENT. If it doesn't work without @SequenceGenerator, IDENTITY might not be supported yet - worth raising a support case to check.

RE: Issue while inserting data in third party data source

komalc3 — Mon, 24 Jul 2017 10:37:17 GMT

Hi Alok

Thank you for replying!
The third party data source is Oracle.

As mentioned in my question, the primary key is a number which is created as "GENERATED AS IDENTITY NOT NULL" in the Oracle data base; the primary key created doesn't have any sequenceName.

Any suggestions.

RE: Issue while inserting data in third party data source

aloks0189 — Mon, 24 Jul 2017 10:31:03 GMT

Hi @komalc one small clarification, which database is getting used by Third Party System like Oracle, MySQL, PostgreSQL etc...

The reason behind asking is, @SequenceGenerator represents the generation strategy as Sequence which is one of the type of generator, and there many databases which do not support Sequence Strategy for PK Generation, such as MYSQL

These are few popular databases which supports Sequence Generation Strategy, such as:

Oracle, SQL Server 2012, PostgreSQL, DB2, HSQLDB etc..

So, if your DB supports Sequence Generation Strategy then try defining this as mention below:

@Id

@Column(name="ID", columnDefinition="NUMBER")

@GeneratedValue(generator="my_seq")

@SequenceGenerator(name="my_seq",sequenceName="MY_SEQ")

Hope this will help you.