syndesisio / syndesis

This project is archived. A flexible, customizable, open source platform that provides core integration capabilities as a service.
https://syndesis.io/
Apache License 2.0
597 stars 203 forks source link

ServiceNow: no update record action ? #3430

Closed mmelko closed 5 years ago

mmelko commented 6 years ago

This is a...


[ x] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Documentation issue or request

The problem

I believe updating existing record (incident,ticket) may be critical functionality for meaningful integration. Is there any reason not having this possibility?

Expected behavior

Screenshot

Request and Response Data

API Endpoints and Schemas

Tasks involved / Steps to Reproduce

1. 2. 3. 4.

lburgazzoli commented 6 years ago

There’s no concept of update/delete using import sets so if the record does no exists it get created, updated otherwhise. deleting a record is not possible throug import sets but you can change its state like setting the inactive field

On Wed, 22 Aug 2018 at 17:45, Matej Melko notifications@github.com wrote:

This is a...

[ x] Feature request [ ] Regression (a behavior that used to work and stopped working in a new release) [ ] Bug report [ ] Documentation issue or request

The problem

I believe updating existing record (incident,ticket) may be critical functionality for meaningful integration. Is there any reason not having this possibility? Expected behavior Screenshot Request and Response Data API Endpoints and Schemas Tasks involved / Steps to Reproduce

1. 2. 3. 4.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/syndesisio/syndesis/issues/3430, or mute the thread https://github.com/notifications/unsubscribe-auth/AByEhRVslFYKrBNWBkBvXr2AKZd95P0Xks5uTXyegaJpZM4WH7KR .

--

Luca Burgazzoli

mmelko commented 6 years ago

I tried "create" record with same sys_id expecting that it will be updated but new one was created instead. I have to double-check.

lburgazzoli commented 6 years ago

try using the sys id generated by the first create

On Wed, 22 Aug 2018 at 17:59, Matej Melko notifications@github.com wrote:

I tried "create" record with same sys_id expecting that it will be updated but new one was created instead. I have to double-check.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/syndesisio/syndesis/issues/3430#issuecomment-415084415, or mute the thread https://github.com/notifications/unsubscribe-auth/AByEhTbLr2wP_TDpBR9EEfG-rstoKcxsks5uTX_OgaJpZM4WH7KR .

--

Luca Burgazzoli

lburgazzoli commented 6 years ago

Another and better option is to set the coalescent key on the import set table:

https://docs.servicenow.com/bundle/jakarta-platform-administration/page/administer/import-sets/concept/c_ImportSetCoalesce.html
mmelko commented 6 years ago

so when I'm using generated sys_id it looks like it's creating new record. But it's possible that I can achieve that with correct importset settings. Don't have any bandwidth to verify now.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!