donderdag 18 mei 2017
[09:54:28]  Rafa de Miguel added jonathan.bueno87 martintaal.
[09:54:35] Rafa de Miguel: Hello Jonathan
[09:54:43] Rafa de Miguel: One question
[09:55:07] Rafa de Miguel: after offlinge when we go to online....
[09:55:15] Rafa de Miguel: how is the BP then created in central?
[09:55:21] Rafa de Miguel: (RCU)
[09:56:27] Jonathan Bueno: Hello
[09:57:15] Jonathan Bueno: I do not understand exactly the case, can you explain me again?
[09:57:22] Martin Taal: the store goes offline
[09:57:29] Martin Taal: the webpos can still work
[09:57:34] Martin Taal: but directly on the store server
[09:57:39] Martin Taal: from webpos a new BP is created
[09:57:50] Martin Taal: what happens then when the store goes to online
[09:57:56] Martin Taal: how is the BP created in the central server
[09:58:04] Martin Taal: by replicating the BP from the store?
[09:58:09] Martin Taal: or through some webpos?
[09:58:20] Jonathan Bueno: Replicating the BP from the store
[09:58:32] Rafa de Miguel: custom webservice?
[09:58:40] Rafa de Miguel: created by us?
[09:58:57] Jonathan Bueno: It is the default synchronization
[09:59:25] Rafa de Miguel: so is symmetricDs who do the job?
[09:59:31] Jonathan Bueno: yes it is
[09:59:35] Rafa de Miguel: ok
[10:00:09] Rafa de Miguel: is enough Martin?
[10:14:06] Martin Taal: okay
[10:14:08] Martin Taal: somewhat
[10:14:10] Martin Taal: yes
[10:14:15] Martin Taal: need to think on something
[10:14:36] Martin Taal: we keep the relation between the BP and the store in which it gets created
[10:14:44] Martin Taal: but we don't replicate this information currently
[10:28:52] Rafa de Miguel: you don't replicate currently?
[10:29:00] Rafa de Miguel: but then Jonathan how is working?
[10:29:16] Martin Taal: we replicate the business partner
[10:29:22] Martin Taal: but not the relation to the store
[10:29:25] Jonathan Bueno: We are replicating the BP but not the tables where the customer is related with the store
[10:29:27] Martin Taal: I need to change this
[10:29:32] Rafa de Miguel: ah ok
[10:29:36] Rafa de Miguel: understood
[10:30:26] Jonathan Bueno: Yes, it needs to be fixed
[10:31:31] Rafa de Miguel: ok
[10:31:39] Jonathan Bueno: Should I report an issue?
[10:32:01] Martin Taal: I will report one
[10:32:04] Martin Taal: and solve it
[10:32:11] Martin Taal: will paste it in the chat here
[10:32:11] Rafa de Miguel: ok
[10:32:21] Rafa de Miguel: give us the issue number so Jonathan can track
[10:32:23] Martin Taal: it is just adding the bp-store-relation table
[10:32:25] Rafa de Miguel: and test
[10:32:29] Martin Taal: to synchronized table
[10:32:36] Rafa de Miguel: and transplant I guess now
[10:32:44] Martin Taal: one directional
[10:32:50] Martin Taal: to replicate from store to central
[10:46:03] Martin Taal: hmm it is more specific
[10:46:09] Martin Taal: than I thought
[10:46:20] Martin Taal: what happens in the following scenario
[10:46:31] Martin Taal: BP1 has a default store Store2
[10:46:42] Martin Taal: in Store1 create a ticket and select BP1
[10:47:01] Martin Taal: do not submit right away
[10:47:08] Martin Taal: central goes down --> s tore1 goes offline
[10:47:14] Martin Taal: submit the ticket
[10:47:18] Martin Taal: ticket will be created in Store1
[10:47:24] Martin Taal: but BP1 does not exist in Store1
[10:47:28] Martin Taal: right?
[10:47:40] Martin Taal: or unsupported (too specific) case?
[10:49:57] Jonathan Bueno: It is not supported, by default we are searching against Store1, so the customer will not appear
[10:50:14] Martin Taal: okay no search in RCU?
[10:50:44] Martin Taal: so no global search
[10:50:48] Martin Taal: but then the BP1 won't be found
[10:50:54] Martin Taal: and it will be created again
[10:50:57] Martin Taal: .
[10:50:59] Martin Taal: correct?
[10:51:10] Jonathan Bueno: If RCU is available we will search against RCU
[10:51:22] Martin Taal: so in RCU it will be found
[10:51:34] Jonathan Bueno: Yes we will find the customer
[10:51:35] Martin Taal: so then my scenario above can happen?
[10:52:09] Jonathan Bueno: Yes it can happen
[10:52:25] Martin Taal: but
[10:52:27] Martin Taal: okay
[10:52:33] Martin Taal: and in normal flow
[10:52:39] Martin Taal: the ticket would be created in central
[10:52:44] Martin Taal: BP would be linked to store
[10:52:57] Martin Taal: and everyone would be synced in one transaction to the store
[10:53:11] Martin Taal: correct?
[10:53:29] Jonathan Bueno: It is not correct, by default customer creation is done in store server
[10:54:00] Jonathan Bueno: And we are forcing the synchronization from store to central to be available inmediatly
[10:54:40] Martin Taal: so the search in RCU will create a BP in store1?
[10:54:58] Jonathan Bueno: yes, the selection of the customer
[10:55:03] Martin Taal: ha okay
[10:55:05] Martin Taal: clear
[10:55:14] Martin Taal: then the scenario I describe above won't happen
[10:55:16] Martin Taal: clear
[10:55:23] Martin Taal: I think then we are good
[10:55:32] Martin Taal: hmm
[10:55:35] Martin Taal: still
[10:55:48] Martin Taal: for my understanding
[10:56:02] Martin Taal: BP1 exists in central, linked to Store2, BP1 has id1
[10:56:22] Martin Taal: when I search from WebPOS (Store1) in RCU it will find BP1
[10:56:33] Martin Taal: when I select BP1 it will created BP1 in the store using id1?
[10:56:46] Jonathan Bueno: Yes, it will have the same Id
[10:56:53] Martin Taal: okay
[10:56:57] Martin Taal: and then get replicated to central
[10:57:03] Martin Taal: but as it already exists in central
[10:57:08] Martin Taal: it won't do anything
[10:57:10] Martin Taal: correct?
[10:57:16] Jonathan Bueno: Yes that's it
[10:57:50] Martin Taal: then I need to do a small change
[10:57:51] Jonathan Bueno: And the next time if the customer is selected from Store2, as the data from RCU are more updated than the local data, we will update BP1 in store2
[10:57:52] Martin Taal: nothing dramatic
[10:58:12] Martin Taal: when a BP is replicated from a store to central
[10:58:18] Martin Taal: also its store-bp relation will be updated
[10:58:45] Jonathan Bueno: Yes, it is the unique problem that I see at the moment
[11:02:57] Martin Taal: https://issues.openbravo.com/view.php?id=36036