Skip to main content

Search

Just upgraded to 3.1.0.2 and can't edit my non-default forms

Answered

Comments

15 comments

  • sdocherty

    Hello,

    I am also receiving the same error that Sandra Huntley is receiving for non default forms.

    I am not sure if Sandra Huntley was creating a new form or if she had imported a form. I do know that I created a new non default form called NEW and then imported my existing DefaultNew.aspx form.

    Could this be part of the problem?

    0
  • sangel40

    Hi, 

     

    Still can't edit any form other than the default New,Display and Edit forms. I also can't add any sub-lists to my form.

    When I upgraded, at some point the license file is no longer being recognised.

     

    I am unable to proceed with most of my forms development because of this issue. As mentioned above we only purchased 2 PRO licenses and would like these reinstated.

     

    Thanks

    Sandy 

    0
  • RosarioM

    Good morning Sandra Huntley,

    Yesterday was public holiday here.

    We would like to inform you that we already read your question, and today we will answer you.
    We just need a little more time.
    Thanks for your patience and understanding.

    Regards

    Rosario Matos

    0
  • sdocherty

    Hello Rosario,

    Do you have any update on this issue as I am alo still in form limbo with this issue?

    Thanks

    Sean

    0
  • RosarioM

    Hello Sean,

    Yes, we have.
    We will place tomorrow a video tutorial to all Community, where everyone can see how to overcome this situation.
    Thank you for your understanding.

    Regards
    Rosario Matos

    0
  • RosarioM
    0
  • sdocherty

    Hello Sandra Huntley,

    Have you tried the fix that was posted for this issue yet? If you have how did it go for you?

    I am having issue in the fact that I have a SharePoint on premise deployment and the video was done on Office 365. The miscellaneous option is missing for me.

    Let me know how you made out.

     

    Thank you

    Sean 

    0
  • sdocherty

    Hello Rosario Matos,

    I have looked at the solution that has been posted and I am having an issue with it. In your video you are using Office 365, but for me I have a SharePoint on premise deployment.

    When I get to the part of the video were I need to edit the web part I am missing the miscellaneous section of the Edit web part as seen in the screen capture below:

     

    I need a suggestion from you as to where to place the copied JS link so that I can get this issue resolved.

    Thank you

    Sean

    0
  • Andreas_Meier

    Dear Sean Docherty

     

    Have you ensured that you have selected the div with property display: none, the id may be different as in the video? Because just on this one we have miscellaneous. These are the steps in the Video from second 6 to second 12 where we "unhide" the needed web part to select the edit for this web part.

     

    Kind Regards

    Andreas Meier

    0
  • sdocherty

    Hello Andreas,

     

    Thank you for getting back to me.

    I did the steps in the video that are displayed from second 6 to second 12.

    This is the element that I have displayed when I am using Google Chrome to look at it through the Inspection option:

     

    When I right click on the Rich Forms Editor to edit the web part these are the only sections that I have available to make modifications in:

     

    I have noticed that at the bottom of the form that I am trying to work with I see the following:

     

    Is this normal behavior for the Rich Forms tool?

     

    Thank you for your help. If it would make it easier I could to a Teamviewer or Skype session to try and resolve the issue?

     

    Sean

    0
  • RosarioM

    Hi Sean Docherty ,

    Thank you for your answer.

    We aren't able to see the images that you post it.

    It seems that this happens only in your environment. I suggest that you open a ticket.

    You can reach us at support@skybow.com.

    and/or

    We are also available via Skype.

    Our Account is - support.skybow

    Our technical team are waiting your contact.

     

    Regards

    Rosario Matos

    0
  • sdocherty

    Hello Rosario Matos,

    I have modified the post to include the screen shots that were missing.

    I will open a support ticket also as per your request. I did reach out to your support team over Skype this morning, but never heard back from them.

    Is this issue that I am experiencing only due to the fact that I am an on premise installation of SharePoint?

     

    Thank you

    Sean

    0
  • m.fostyak

    Hello Sean!

    Sorry for the late reply. The problem is that you are selecting wrong web part. There multiple div elements with id="MSOZoneCell_WebPartWPQ{x}". And you should select the one that has property display: none. and Then follow the tutorial. 

     

    If you will need any assistance with this, please feel free to contact skybow support.

    Best Regards

    Markiyan Fostyak

    0
  • sangel40

    Hi Sean,

     

    Yes, I have been able to apply it to all of my O365 non-default forms.

     

    Hope it goes well for you too.

     

    Kind Regards

    Sandy

    0
  • sdocherty

    Hello,

    Here is how I fixed the issue that I was having with the No Valid License error message. I would like to add that the way I dealt with this issue fixed the issue I was having with the form. Please make sure that you have exports of your forms or screen shots in case you need to recreate a form.

    Also, this is a solution that worked for me. Please all information carefully as this solution might not work for you. If after reading this post you are still not sure, contact skybow support. The skybow support team is awesome and extremely diligent and helpful.

    The text below is from a Skype session with skybow support that I had initiated.

     

     

    I am looking at the video that you have posted here for me to review. In the original video that was posted to solve the issue I was able to find the options that needed to be unchecked (display options) and I did uncheck them.
    After unchecking them I was still not able to complete the rest of the steps that were outlined in the original video to fix the issue.
    Okay as a thought I have done the following to resolve the issue that I was having with working on a new non default form.
    The original non default form that I was working with was imported into the form once I had created the new non default form called New.
    The form that I had import was a form that I had originally created in Ardevia Rich Forms and then brought into skybow Rich Forms. I think that this old imported form might have been part of the issue or contributed to the problem that I was experiencing with the non default form.


    So, I did the following today as a hunch to see if I could recreate the issue that I was having.
    1. I opened the site in SharePoint Designer and deleted the form that I had called New.aspx. This was the form that I was having the issue with trying to edit as I did not have the Rich Forms controls available and I was getting the error message about not having a license.
    2. In SharePoint Designer I found the New.aspx form and deleted the form.
    3. I went to the list and opened Rich Forms to confirm that the New.aspx form did not show up in the list of forms that I could edit. It was not there as an option to edit.
    4. I went back into SharePoint Designer and created a new non default form called NewPO.aspx. This form is not set a default form at all.
    5. Then I went back to my SharePoint list and opened Rich Forms and confirmed that the form - NewPO.aspx - was in the list of forms that I could edit. It was in the list and I selected the NewPO.aspx  form and opened it into the Rich Forms environment. This form opened successfully and all of the controls to modify the form were available to me.
    6. I have been able to successfully make some changes as a test to the NewPO.aspx form that I have created and I have not received a license error message in this form at all.
    I believe that the issue has been solved for me and that the support ticket can be closed. My feeling is that importing the old form caused part of the issues that I was experiencing with the Rich Forms product.
    I will now just work with the NewPO.aspx form that I have created and rebuild my form this way instead of importing any version of the old form.
    I want to thank your support staff for all of their support and prompt attention to assisting me in this issue. It is very much appreciated.

     

    Again I want to stress that this solution worked for my issue that I was having. Please read the solution carefully and if you are uncertain about doing the above steps. PLEASE reach out to skybow support. They are the professionals and they are there to help you.

    0

Please sign in to leave a comment.