Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

DB Accounts full import behaves as incremental import

JonasSallstrom
New Contributor II
New Contributor II

Hi all, 

We have some problems where full accounts import job from Database behaves as if it was an incremental job and appends the incrementalcolumn to the sql query. Guessing this shouldn't be expected behavior? 

Any suggestions on what we need to change to get the full import to behave as a full import again and having the incremental as incremental?

Thank you in advance

 

Account Import XML defined in the connection

<dataMapping>
    <sql-query description="This is the Source DB Query" uniquecolumnsascommaseparated="name" >
        <![CDATA[select 'Placeholder' as SECURITYSYSTEM, 'Placeholder' as ENDPOINT, '1' as isActive, EntitlementId, EntitlementCategory, AnotherId, GCId, CreatedDT, UpdatedDT from sav.SAV_Mapping
where AnotherId not in (select AnotherId from sav.SAV_Identity where CountryCode = 'DE')]]>
    </sql-query>
    <mapper description="This is the mapping field for Saviynt Field name" accountnotinfileaction="suspend" deleteaccountentitlement="true" ifusernotexists="noaction" addOnlyMode="false"  dateformat="timestamp" incrementalcolumn="UpdatedDT" systems="'Placeholder'">
        <mapfield saviyntproperty="accounts.name" sourceproperty="AnotherId" type="character"/>
        <mapfield saviyntproperty="securitysystems.systemname" sourceproperty="securitysystem" type="character"/>
        <mapfield saviyntproperty="endpoints.endpointname" sourceproperty="endpoint" type="character"/>
        <mapfield saviyntproperty="entitlementtypes.entitlementname" sourceproperty="EntitlementCategory" type="character"/>
        <mapfield saviyntproperty="entitlementvalues.entitlementvalue" sourceproperty="EntitlementId" type="character"/>
        <mapfield saviyntproperty="accounts.status" sourceproperty="isActive" type="character"/>
        <mapfield saviyntproperty="accounts.customproperty1" sourceproperty="AnotherId" type="character"/>
        <mapfield saviyntproperty="accounts.customproperty2" sourceproperty="CreatedDT" type="date"/>
        <mapfield saviyntproperty="accounts.customproperty3" sourceproperty="UpdatedDT" type="date"/>
    </mapper>
</dataMapping>

Job Config

JonasSallstrom_1-1702373239088.png

 

 

Log from Accounts Import (Complete) from Database job.

JonasSallstrom_2-1702373432944.png

 

 

4 REPLIES 4

armaanzahir
Valued Contributor
Valued Contributor

@JonasSallstrom ,

This seems to be a bug, it's not normal behavior. 

It's only when the job trigger type is incremental, should it pick up the incremental column defined in the xml and process accordingly. 

Better to raise a support ticket for this. 

Just for your scenario, can you define a dummy column name as the incremental column in the xml and check whether the import runs as a full import?

 

Regards,
Md Armaan Zahir

Changing the incremental column from 'UpdatedDT' to 'dummy' made the full import behave correctly.

With the caveat that the dummy column doesn't exist in the queried table.

armaanzahir
Valued Contributor
Valued Contributor

Still a bug, better to raise a support ticket for this. 😊

 

Regards,
Md Armaan Zahir

JonasSallstrom
New Contributor II
New Contributor II

Support ticket has been raised, will post any solutions to issue in this thread to help others with similar issue.