v 8.9.0.0 and ODP & many-2-many

Hi,
I am facing different issues with ODP's implementation with many-2-many dataview fields:

- in create views:
--- not every dataview field refresh after inserting records
--- business rules are not recognizing @fields as it did before ODP
--- setting session values is not working
--- some many-2-many dataviews hang and freezes the app

- in edit views:
--- changing records in many-2-many dataviews changes the form to edit mode and if you do not SAVE, the changes to the dataviews are canceled.

I am not sure what exactly are the interactions AND changes introduced to the app when 'offline' settings in a page enabling ODP therefore reluctant to start app wide changes to alleviate the errors.

Does anyone face the same problems or have an advice?

Thank you
1 person has
this problem
+1
Reply
  • I'm still waiting for the .dll :(

    And now I'm concerned as I use the many-to-many dataviews a lot.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Ossama,

    Are you referring to many-2-many fields in "...many-2-many dataviews...""? Our testing of m2m fields shows that everything works correctly.

    We are preparing a collection of video tutorials explaining how Offline Data Processor (ODP) works and how Offline Sync makes things work in disconnected mode.

    You can try ODP right now by selecting "Offline" checkbox on any page of your app.

    You will observer that child DataView fields are displaying if present in createForm1 views. ODP is immediately engaged in "new" mode.

    ODP is not engaged in "view" mode until a change is made to a child DataView field. The app works as it did prior to release 8.9.0.0. If a child record is changed then data starts being accumulated on the client. If you change a child row then the main form will switch to "edit" mode. You will need to save (commit) the master record for all changes to be saved.

    Actions New and Calculate are executed on the server when ODP is engaged.

    ODP is always engaged in "offline" mode with Offline Sync. All actions are executed on the client only.

    See anwers to your questions below:

    Q - in create views:
    --- not every dataview field refresh after inserting records

    A. Please explain the steps to reproduce that.

    Q. --- business rules are not recognizing @fields as it did before ODP

    A. What kind of business rules are not working in your apps (command,phase, etc.)?

    Q. --- setting session values is not working

    A. How do you use the session variables in your app?

    Q. --- some many-2-many dataviews hang and freezes the app

    A. We believe that you are referring to DataView fields here. Most likely you are experiencing an exception. Try reproduce the problem in Chorme and activate developer tools to see the error.

    Q. - in edit views:
    --- changing records in many-2-many dataviews changes the form to edit mode and if you do not SAVE, the changes to the dataviews are canceled.

    A. This is the behavior by design. ODP wraps your entire data editing session. Data changes are not sent to the sever until the master record is committed. Making a change to a child record will require additional confirmation via Save of the master. User can also opt to cancel the changes in child dataview fields by cancelling the master record.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Thank you for the thoughtful response.

    Yes I am referring to DataView fields.

    Q - in create views:
    --- not every DataView field refresh after inserting records
    When inserting a NEW record, it saves but the DataView field does not reflect the record I just added while still in edit mode. If I SAVE however, the record is saved and is listed if I reopen the detail page.

    Q. --- business rules are not recognizing @fields as it did before ODP
    Calculate/Execute/SQL

    Q. --- setting session values is not working
    When a lookup field is changed, a calculate sql execute business rule runs to set the value in a session variable to be used to filter the grid view used for another lookup field.

    Q. --- some many-2-many DataView fields hang and freezes the app
    They worked before I upgraded though. I will troubleshoot this and report what I found.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Q. --- some many-2-many DataView fields hang and freezes the app

    Troubleshooting confirmed that the Context Fields filtering causes the error in the screenshot. The filtering worked prior to v8.9

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Q. --- setting session values is not working

    Troubleshooting shows 2 issues:
    grid view filtering using Filter Expression is not working at all even with static expression (fieldName = 'value')

    Also, the @field whether current field or setting Session value, assigns the alias not the field value. ex:
    if setting ID to @Session_ID, if the ID has a "Name" field as alias, the @... value is the "Name" field value not the ID which is not the expected behavior. This also happens when using {ID} in category description etc.

    It is important to mention that this happens only in create view when 'offline' is activated. BUT in edit view, all is ok.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

    • Ossama,

      The exception in your screenshot displays the line in the minified JavaScript library.

      Do the following:

      1) Change line 26 in ~/app/web.config file to read: <compilation debug="true" ....>.
      2) Try reproducing the error one more time.
      3) Attach the screenshot of the call stack and the same screenshot that you have attached above. It will show the line in the source code causing the problem.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Hi,

    I am experiencing also freezing of many-2-many Dataviews when creating child records in a Master-Child Controller... This did not happen with previous release.
    I activate odp in touch-settings.json file...
    Any Support?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Excuse me, I meant one-to-many relationship in database with transactional data Input.

    I just have a Master-Child controller. The primary key of my master table is provided to a dedicated field in the child table in a one-to-many relationship.
    I just activated "offline" on the page containing the controller to have transactional data input enabled. Everything appears to work fine, the main table is recorded and also the child data usint the transactional data input. However, the website freezes after saving process... The black message box indicating that the record is saved on bottom of the page remains there.... I need to refresh the page to get again functionality.
    Sorry for not providing an example in the Northwind database, but I am in a hurry and the problem seems rather simple.
    Let me know if it is still needed to provide the example or if you could provide some tips with this information.
    Thanks in advance!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • BTW,

    I use .NET Framework 4.6, Microsoft SQL Server 2014 and Chrome.

    I tested more the above issue, and it happens randomly... Not allways. This is what is making me very confused...

    With COT Release 8.7.14 I did not experience this issue. I will roll-back to previous release and try to verify.

    Regards
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Hi, I just catched an error when the Browser freezes after saving the Master-child record. Note the screenshot:

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Hi,

    Thanks in advance for the support on this topic. I was trying to reproduce the error one more time with debug activated. Curiously, it is not possible to have it happen in debug mode.
    I deactivated debug again and tested. Then I had the problem again. As said, it does not happen continuously, but at certain save operations the site freezes...
    Following the pictures of the last error reproduced wiht debug mode off, although they might not be helpful as there is nothing to see in the call stack...
    I am really not sure what might be the cause....

    • Luis,

      The error in the log is the part of normal operation.

      Data requests to the server are passing a login token in Authorization header of each request to read data. The token expires every 15 minutes. The server denies access with 401 HTTP error. The app renews the token by making a silent "Login" request and retries the failed request.

      The freezing may have to do with the error that was fixed in ODP in release 8.9.1.0.

      If you are able to reproduce the error consistently then please record the steps, open a ticket, and let us know your availability. We will have our expert do troubleshooting on your computer over Webex.

      If you can make screen recording that shows the error then that would be helpful as well..
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Here comes v8.9.1.0 with listed ODP fixes that do not address the issues above.
    the "offline" toggle at the page level is super frustrating. It makes every New action of dataview fields behaves in offline mode even if the record is opened in editForm1, it is still act offline.

    Not to mention freezing the app, not checking for duplicates.
    New issue: if a dataview succeeds in adding one new record, the second one freezes the app.

    I recommend a way to apply ODP at the view level.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated