Hi,
I just wanted to know, if it's common/possible to use the same MBOs for hybrid and native applications. The problem I'm facing is correct data limitation to the device.
Let's say I have a MBO based on the following data table with 1000 rows:
| ID_Customer | FirstName | LastName | City |
|---|---|---|---|
| 1 | Jon | Test | Hamburg |
| ... | |||
| 1000 | Ron | Pattberg | Berlin |
Requirement: The device should show all customers for a specified city.
For native App: I create a synchronization parameter for the attribute "City". By setting the synchronization parameter to "Hamburg", only customers of Hamburg will be downloaded to the device.
For hybrid App: Since synchronization parameters are unavailable in HWC Apps, I need another mechanism for filtering data. So I create an object query findByCity for this MBO. The problem here: All customers will be downloaded to the device, and the object query just filters the data (or am I wrong?). In HWC examples, personalization keys are used in load arguments for filtering data. Mixing both synchronization parameters and personalization keys for native and HWC apps doesn't seem to work.
So is there a correct way to use one MBO in hybrid and native application or are the purposes of native and hybrid apps differing too much, that a single MBO can't fit both needs?