hi there is a problem with the list of values for the single selection field

Description

Good day fo you!

Hi there is a problem with the list of values for the 'single selection field'

i make field and include strategy

I am maked select SELECT [ProjectUnid] , LeadName FROM [KROP].[dbo].[v_ActiveProjectLead] WHERE TypeLeadID in (7) and recive 180 values

it is wrong byt i have create new 'single selection field' and recive 298


and it is true ....

How i can fix it ?

Best Regards Alexey.

Environment

None

Activity

Show:
Deniz Oğuz
July 20, 2019, 8:23 AM

I may not understood your request correctly, so I will repeat what I think.

  • You have two custom fields both are using the same "DB Synch" configuration"

  • When you synchronize, one of them updates 298 option but the other one only updated 180 options

Although both fields are using the same configuration this may happen in the following situation. There is another table, ####_EX_OP_INFO. This table stores extra information about each record synchronized for all db synch configurations. FIELD_CONFIG_ID and FIELD_ID columns determine which custom fields a record belongs. DATABASE_ID column in this table shows which DB record this option maps to. When you synchronize this DATABASE_ID column is checked agains ID column you have selected in synch. config. In your case ProjectUnid column. Could you check ####_EX_OP_INFO column for both field configurations that may cause this behavior? Sorry, this may take time but there is not much I can do remotely without extra information.
You can also enable extra logging and check how synchronization is performing by inspecting the logs.

Alexey Gorya
July 22, 2019, 9:43 AM

HI We have solution

 

DELETE FROM AO_00C882_EX_OP_INFO t WHERE t.ID IN ( Select id from ( SELECT a.ID, b.CUSTOMFIELD FROM AO_00C882_EX_OP_INFO a, CUSTOMFIELDOPTION b where a.field_id = 20402 and a.OPTION_ID = b.ID(+) ) where CUSTOMFIELD is null )  

 

​ after remove link to null CUSTOMFIELD all synk wery well.

Deniz Oğuz
July 22, 2019, 12:45 PM

Hi ,
Thanks for the update. I'm living this issue open for a while, because we still don't know what caused the corrupted db state.

Alexey Gorya
July 22, 2019, 12:59 PM

May be affect type of synchronization “Delete“

 

Alexey Gorya
July 22, 2019, 1:00 PM

initially there was a synchronization strategy with the removal of values

Assignee

Deniz Oğuz

Reporter

Alexey Gorya

Labels

None

Source

None

Jira Version

1.8

Database Type/Version

Oracle and MSSQL (as a data source for a field)

Browser Type/Version

None

Affects versions

Priority

Major
Configure