How to insert data from interface to table?

Hi,

Please call the following smart service rule in the saveInto list i.e. {  }

a!writeToDataStoreEntity(
dataStoreEntity: cons!DATA_STORE_ENTITY,
valueToStore: ri!rule_input )

Thanks

Thanks for Quick reply.

But, I want to pass below rule inputs to table:- 

1. LeaveRequest (Text)

2.EmployeName(Text)

3. EmployeeEmail(Text)

4.StartDate(Date)

and table is having ID column which is auto generate. In this case how i can pass in to ValueToStore? 

I'm not exactly sure what you're still missing, but if this is any help, for an auto generated field (i.e. primary key id), you simply leave that field blank in your CDT when writing to data store, and the value is assigned properly during database write.

How to pass multiple filed values to table?

a!writeToDataStoreEntity(
dataStoreEntity: cons!DATA_STORE_ENTITY,
valueToStore: ri!LeaveRequest, ri!EmployeName, ri!EmployeeEmail, ri!StartDate) ?

You have to create a separate rule input for a cdt which typed of the CDT, you have created. Then save all the fileds in this single CDT typed rule input and pass this rule input to valueToStore. 

Thanks

Why are you storing the values in separate ri! variables instead of in a single CDT ri! variable? 

If you have a specific/important reason to do it that way, then we can handle your use case with one or two extra steps, but if you don't need those separate rule inputs, then your values should just be saved into the fields of a CDT rule input then you just reference the CDT within your write to data store.

Value to store has to be the same type as the CDT used to create the datastore.  You need to make a custom datatype with the values that you need, then input one of those as the valueToStore.

ri!leaveRequest.employeeName, ri!leaveRequest.email, ri!leaveRequest.startDate, ri!leaveRequest.endDate

then your database write is just a!writeToDataStoreEntity(datastoreEntity: cons!DATA_STORE_ENTITY, valueToStore: ri!leaveRequest

)

All the other fields are already inside the leaveRequest CDT.  It's got everything you need contained in one place.

If you have a strong need to store the inputs in separate rule inputs, you could merge them all together at the end into a leaveRequest by using the type constructor as your value to store.  Honestly I agree that's most likely an extra unneeded step in this instance.