Solved

Mobile Initialize doesnt create table

  • 27 April 2021
  • 5 replies
  • 197 views
M
Rank
Userlevel 1
Badge +3

Hi,

     I have created a Sync Rule with delivery mode as Batch Delta and everything runs fine until the Mobile is initialized ,After initialization no data is there in the table and the data gets pushed the next time the sync rule runs.

Is the app not supposed to download data for all tables when it is initialized for the first time.Am i missing something,Any guidance would be appreciated

icon

Best answer by Lee Pinchbeck 27 April 2021, 12:30

View original
This topic has been closed for comments

5 replies

S
Rank
Badge

Hi, Could you please have a look on the Aurena Native Logs in IEE./Aurena. that will indicate if you have any errors. s.a. invalida packages or data mismatch.

Lee Pinchbeck
Rank
Userlevel 7
Badge +24

Hi @manishpandey,

It may be helpful if you are able to upload a screenshot of your sync rule and the script added in the initial query.

The initial query is what runs on initialisation so that would be the first point to check if the data is not coming through correctly.

Try comparing the new query to an existing sync rule.

Kind regards,

Lee Pinchbeck

Currently reading: The Way of Kings - Brandon Sanderson
M
Rank
Userlevel 1
Badge +3

Hi Lee,

            I have attached the screenshot here and also the query which is configured to run at initialization

 

<hierarchy_select return_only_requested_attrs="true" max_rows="50000">
  <primary_table>c_iot_device_ext</primary_table>
  <from>
    <table>c_iot_device_ext</table>
    <table>product</table>
  </from>
  <attrs>
    <attr>C_IOT_DEVICE_EXT.EXT_HOSTNAME</attr>
    <attr>C_IOT_DEVICE_EXT.EXT_IP_ADDRESS</attr>
    <attr>C_IOT_DEVICE_EXT.EXT_MAC_ADDRESS</attr>
    <attr>C_IOT_DEVICE_EXT.EXT_LATEST_TOTAL_COUNTER</attr>
    <attr>C_IOT_DEVICE_EXT.EXT_LATEST_COLOR_COUNTER</attr>
    <attr>C_IOT_DEVICE_EXT.EXT_LATEST_BLACK_COUNTER</attr>
    <attr>C_IOT_DEVICE_EXT.EXT_LAST_CONNECTION_DTTM</attr>
    <attr>C_IOT_DEVICE_EXT.DEVICE_ID</attr>
    <attr>C_IOT_DEVICE_EXT.EXT_IOT_MONITORING_TOOL</attr>
  </attrs>
  <where>
    <join_constraint>
      <constraint>
        <left_operand>PRODUCT.SERIAL_ID</left_operand>
        <operator>EQUI</operator>
        <right_operand>C_IOT_DEVICE_EXT.DEVICE_ID</right_operand>
      </constraint>
    </join_constraint>
    <constraint>
      <left_operand>C_IOT_DEVICE_EXT.EXT_ACTIVE</left_operand>
      <operator>EQUI</operator>
      <right_operand>Y</right_operand>
    </constraint>
    <constraint>
      <left_operand>C_IOT_DEVICE_EXT.ext_hostname</left_operand>
      <operator>not_null</operator>
    </constraint>
  </where>
</hierarchy_select>

 

 

The query runs fine vial xml poster and also the data gets synced when the job runs every houe,but no data is coming at initialization

Lee Pinchbeck
Rank
Userlevel 7
Badge +24

Hi @manishpandey,

Am I correct in assuming EXT indicates this is an extension table? If so, please see this other thread:

extension tables should not have their own sync rules and should instead be setup to be included in the sync rule for the table they extend.

Kind regards,

Lee Pinchbeck

Currently reading: The Way of Kings - Brandon Sanderson
M
Rank
Userlevel 1
Badge +3

Hi Lee,

            I made the changes so that the sync rule now triggers on the parent table and not the ext table but the main issue is still there,it is not replicating at time of initialization and only happens after the schedule runs at the specified frequency ,Do we need to add the reference of the sync rule somewhere else as well ?

Terms & ConditionsCookie settings