I've automated filling a formulary developed with Microsoft Forms but sometimes it works and sometimes don't.
Originally changing from one input field to another just requires sending a TAB. I do that in Autohotkey with the command:
Send , {TAB}
What I've found is that sometimes the "area" of a question can be selected, and sometimes it does not.
When the area of a question can be selected, I must send two TABs to change from the current input filed to the next one:
Send , {TAB 2}
I'm currently using Microsoft Edge, but I've also used Firefox and Google Chrome and the behavior is the same. It's funny that the first time I tried Firefox, or Chrome the question areas are not selectable but after refreshing the form (F5) the question areas become selectable.
I've also tried closing the browser and even turning my computer off and restarting it again.
**But the behavior is always the same: ** Sometimes the question areas are selectable and sometimes don't.
I don't know if it is a browser configuration (I think not because different browsers exhibit the same behavior).
Even, it could be the form rendering from Microsoft or any other thing I really don't know.
I just don't want to have two Autohotkey programs for filling the same form, one used when question areas are selectable and other for when question areas are not selectable.
So, any help would be appreciated.
Kind regards,
J.
It seems that when you are logged in your Microsoft 365 account then question areas are selectable and when you are logged out, they are not.
So, to avoid question areas to be selectable (and need an additional tab in autohotkey) you just need to be logged off from you Microsoft 365 account and that's all.
So, to fill my form automatically I log off from my Microsoft 365 account and run my autohotkey script and it fills the form correctly.
Seems odd, but it is working for me, and this is better than having two scripts for the same Microsoft Form.
J.
Related
I am developing an add-in for outlook 2013/2016.
Thus far I've been using vbscript for my forms.
However, needing not to have code exposed to anyone
who knows how to hit'design this form' and for easier
upgrading I was considering to switch to formregions.
My problem is how to assign the properties of a control
created in c# form region in the way that is done in outlook forms
(that are meant to contain form regions)
But I cannot find any help and references for that purpose
Does anyone know of a workaround?or some documentation, maybe?
PS:Importing the form region results in error:
'The installation Path for outlook 15 cannot be determined'
(I am running vsto 15 in office 16 64-bit)
thnx for all the effort!!!
the conversation got quite long
and i am gratefull.
i have taken your answers into
account but i could not complete
the puzzle starting from all
of the points you made.
Instead i will answer this question
with a complete tutorial i found.
Actually it dates back to office 2007
(so i avoided it initially because,
you know, technologies change
but i tried on 2016 and verified it works!!!
the link is at :
http://www.informit.com/articles/article.aspx?p=1327185
You can persist any property on an item using PropertyAccessor.GetProperty/SetProperty or the UserProperties collection.
I have to build some cascading multi select input controls in JasperServer Report, but I'm having the same problem as this guy here:
http://community.jaspersoft.com/questions/844760/creating-cascading-input-control-multi-select-input-control
The thread is very old, and people replied him to search for a "Cascading_multi_select_report" sample. I've searched for it, but I couldn't find it anywhere.
I'm struggling to make this type of cascading input control... Does anyone have any idea?
Thanks!
I don't have an answer for this, but I may have an answer to help you debug. Whenever you are trying to run your report on the jasper server and are just getting a blank page (no input controls), you can use Chrome developer tools or Firebug or whatever browser web developer tool you use (usually Ctrl + Shift + Q will pull it up) and in the Network pane, you can see the requests. Find the last GET request, and look at the response for it and you can see the error.
I have created a standard google form and added a record. i have set options to edit the response . one of the questions i have added allows me to jump straight to submit or continue editing .
However When i am editing a response and i choose the my option to jump to submit and then press submit , i find the information is lost when i go back to edit the response.
However if i scroll through all my answers and submit at the end, then the data is saved.
Is there an issue with google forms ? i am not using any scripts - it is standard editing and form options.
This appears to be an issue with Google Forms when editing responses and changing the "go to" path from the initial submission. I've opened a question with a Google "Community Specialist" in the Google Help forums but so far she has not identified how to avoid this problem nor reported escalating it to get it fixed.
For those curious what to avoid, here is the scenario that causes a form to lose data:
Create a form with multiple Go To paths
Fill out a response using one Go To path of questions
Submit response
Click Edit Response
Choose an option that takes you down a different Go To path of questions
Submit the edited response
Click Edit Response
Going back to the original option Go To path, the earlier submitted data will now be gone.
Here is a form I've created that demonstrates the issue.
Here is the thread that as of this writing the Google Community Specialist has not yet solved. Perhaps if more people were to comment that it really is an issue she will pay more attention to it and bring it to the attention of who might be able to fix it.
my company's software product has a feature that allows users to generate forms from Word templates. The program auto fills some fields from the SQL database and the user can fill in other data that they desire. So we have a .dotx template that holds the design of the form, and then the user gets the .docx file to fill out when they call it from our program.
The problem we're having is that some of our users have been finding that the forms take an exceptionally long time to open up and then, once open, are so slow to respond (scroll around, etc) that they're unusable. So in my investigations so far, I've found out that the problem systems are one with lower powered CPUs (unfortunately it happens for systems above our system requirements) and the Word forms that cause the problems are ones with large amount of ActiveX style checkboxes on them. I verified that reducing the ActiveX checkboxes fixes the form loading problems.
So I have the following questions about solutions (we're using Word 2007):
1) Is there any way to configure Word, or some other settings, so that there won't be such a strain opening a Word form with lots of ActiveX checkboxes? Any way of speeding up Word's opening?
2) Using Legacy style checkboxes instead of the ActiveX ones makes the forms load fine, but it looks like the user has to double-click the checkbox and change Default Value->Checked. Is there a way to configure it so that they can simply click on the checkbox to tick it? "Legacy Forms" checkbox as a name kind of worries me (Legacy…), does that mean a future version of word at some point wouldn't load the checkboxes because they're "legacy"?
3) Yes, it became clear to me after a little bit of research into solutions that Word is not the tool for the job for forms like I'm describing. InfoPath seems to be exactly what we should have been using all along but unfortunately I wasn't involved in the decision making or development of these forms, just tasked with coming up with a solution.
I'd appreciate answers to any of these, or if anyone has any other ideas for solutions to this problem.
Thanks
I'm about 3 years too late, but if you want a legacy checkbox to act like a checkbox, you have to restrict editing on the document or section. (You can lock just a section, if you want.) Locking--on Word 2010 it's called "Restrict editing"--is an option under either the Developer tab or the Review tab.
If you restrict editing in this way, the user cannot edit the text but can fill in the form field, so if the form field is a checkbox, the user can click the checkbox on or off; if the form field is a text box, the user can fill the text box.
If you choose to lock off just a section, you'll probably want to use continuous section breaks (Page Layout > Breaks > Continuous) and specify which section. (In the space where you choose form editing as your kind of restriction, there's a small link that lets you specify which section or sections are locked.)
I know pop ups are not good and should be avoided if possible but is that really true that now, whenever i think of using a pop up, i should always be considering other options? Are there any exceptions? And the last question is: what is the default replacement for pop ups?
You can use any javascript based dialog. Look for example at jQuery UI Dialog
The "Web2.0" pop-up might be a lightbox. I hope these are just a passing fad, because they are kind of annoying (a lot like pop-ups).
http://en.wikipedia.org/wiki/Lightbox_(JavaScript)
Banners, like you get at the top of Stack Overflow to tell you about badges, comments, see the FAQ if you're a new user are my favorite. They don't really get in the way and can link to the main content.
It depends on what you are trying to accomplish. Pop-ups are completely acceptable in certain contexts. The aversion to pop-ups arose from having pop-up foisted on users in the form of advertisements. I think that pop-ups are still a valid device in the correct case.
My rule of thumb is to not make any decisions for the user that they can make themselves. This typically includes opening a pop-up since they could right-click and choose "open link in new window" if they so desired.
Do you want to capture of a piece of user input without allowing any further interaction? A modal dialog is your friend.
there are cases where you want to offer a bit of useful info or a quick reference that doesn't necessitate closing off the rest of the web page or navigating to a different location. This could be addressed using some javascript and floating div's but many times a pop-up will do what you want without being obtrusive to a user.
I tend to read resources from the likes of 37 signals and UIE to keep up with the best ways to enhance user experience without alienating a user.