Search results for 'cascading list using sharepoint list'

How best to present multiple multi select choices based on a number of other fields data

markikav — Thu, 12 Aug 2021 05:54:11 GMT

Hi InfoPathdev community! Hopefully someone has had similar use case to this and point me in the right direction. I have a service request process with the data stored in a sharepoint list and data entered via Infopath form on the sharepoint site (they have infopath 2013). The service request "case" can have multiple requests in it based on Service Line and Scenario, we allow them to enter 6 requests. Example Request 1 Service Line 1 = Transaction Queries Scenario 1 = One Payment - Additional Info Request 2 Service Line 2 = Transaction Queries Scenario 2 = One Payment - No Additional Info Request 3 Service Line 3 = Payments on Hold Scenario 3 = Email to Customer Request 4 Service Line 4 = Direct Debits Scenario 4 = Cancellation Request There are 25 Service Lines all with 5-10 Scenarios which I have configured using a sharepoint data connection with cascading dropdowns and works nicely (thanks to this forum!) Last part of this is that they want the ability to QA how the request was dealt with by an offshore team, so per service line they have defined multiple error scenarios that they want to rectify, these are multi select. So what I want to do is in a QA view in the form present them with one instance of the Service Lines errors multi select fields based on the Service Lines selected in the main requests. Example as per above , there was 4 requests but only 3 Service Lines, so I want to present the Error fields multi select boxes now for the 3 Service Lines.. E.G Service Line = Transaction Queries Errors = Incorrect Template , Incorrect info provided, No Follow Up and all 3 could apply or just 1 or 2 etc i.e. multi choice select and this would cover the 2 requests made There is probably a crude way to do it which I'm trying to avoid as I will need multiple extra fields with tons of sections to hide I would imagine! Any help here on a good approach appreciated. Thanks Mark

FormsViewer Training Package (August 2019)

Kervi Alfafara — Tue, 20 Aug 2019 14:10:45 GMT

FormsViewer Training August 2019

In this training, we'll introduce you to FormsViewer - a tool we developed so you can retain your existing InfoPath investments by:

#1 - Helping you migrate your InfoPath forms in a web browser

#2 - Extending your form solutions for today's business needs

#3 - Creating responsive mobile-friendly view with cascading style sheets (CSS)

#4 - Adding missing features to your forms quickly - map repeating data to lists, print PDFs, glass signatures, resize images, and many more!

We're also introducing some of the new features added in FormsViewer latest version (4.1).

Download the complete training package here.

Watch the training playlist here.

Training Contents:

Day 1

Review Basics
- Deploy a sample form to your site
- Submit and refresh repeating items to/from a SharePoint list
- Add a responsive UI to high resolution mobile devices
- Insert and delete rows in a repeating table with picture buttons
- Print a PDF from your browser form
  - New Print repeating data from a list forms

Day 2

Add New Features
- New Streamline processing and increase security with Authy
- Updated Fill common gaps faster with our template part
  - New Auto-log out inactive users and save their edits
  - Updated Speed up dev-prod pushes with dynamic data connections
  - Updated Debug your forms with a secret button in the footer
  - Store change history for auditing
  - Upload attachments and replace with links
  - Make it easy for users to submit suggestions

Day 3

Validate Input / Format Output
- New Date & Time calcs – easier formatting for humans
- New Form Validations – enforce higher quality human input
- Build a dashboard for process management

Day 4

Get Fancy
- Prompt users for input with a popup dialog
- Display an overlay on top of your form with details or a choice
- Resize images using a new AlterImage command

Re: Infopath 2013 forms failing in Sharepoint 2013 (but no changes made to form design)

JdSCymru — Tue, 09 Jul 2019 14:40:27 GMT

Hello, thanks for your reply.

The forms are all browser-based for a mix of Windows 7, and Windows 10 users.

Each form 'type' (either using just date/text, or date/text/number) uses an xml data source to support cascading lookups, and each SharePoint list is linked to Access 2016

We are currently upgrading all users to Windows 10 this year.

It appears (but I still need to confirm with the users) that (at least some of the) Windows 7 users are entering data as expected for 'date/text', and 'date/text/number' based forms.

For the affected Windows 10 users: they can submit the forms as expected IF the InfoPath form uses only 'date' and 'text' fields.

However, if the Windows 10 user submits for an Infopath form also using 'number', then 'Unable to submit is shown' - even though no validation is present in the Form or List.

Regards.

Regards,

Jonathan

Re: Cascading Drop-down Value not Auto-populating Additional Fields

Jacob Russ — Wed, 14 Nov 2018 15:12:37 GMT

Yeah, that's the formula I have been trying to get to work on both the check box as well as the drop-down Country4, to no avail. :) Which simply means no value is populated in Edoc_Delivery_Notes when the check box is ticked, nor when a value has been selected from Country4. The formula resolves fine without any errors otherwise. I am wondering if the complexity I have implemented, using cascading filters for Country and Sales Org (based on Region and Country respectively) utilizing lookup columns in two different SharePoint list data connections is making it hard for me to connect to the Default-Values SharePoint list for these additional 16 (sorry - not 8, not 18 - all 16 Edoc fields).

Also, I am able to get Payment Terms, Inco Terms 1, Inco Terms 2, and Shipping Conditions to all auto-populate from Sales Org, but when applying the new formula, I am unable to get default values from Country for some reason.

xdXDocument:GetDOM("Default-Values")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:Payment_Terms[../d:Sales_Org = xdXDocument:GetDOM("Sales_Orgs1")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:ID[../d:SOCountryLook = xdXDocument:get-DOM()/dfs:myFields/dfs:dataFields/my:SharePointListItem_RW/my:Country4]]

FormsViewer Training Package (Sept 2018)

Jo-Anne Alfafara — Tue, 02 Oct 2018 15:21:16 GMT

In this training, we'll be teaching ways on how FormsViewer can help you migrate your InfoPath forms in a web browser and demonstrate how you can open your forms in SharePoint's modern UI. We'll show you how to use FormsViewer Designer, where you can modify your templates in the browser without InfoPath and add dozens of new possibilities: generate forms in PDF format, upload file attachments to document libraries, submit and refresh your repeating data to SharePoint lists, add cascading style sheets (CSS), and more! See what's included in this training package:

Training Contents and Video Links:

Day 1:

Lab 1 - Submit and Refresh Items to a SharePoint List
Lab 2 - LoadResource
Lab 3 - Insert and Delete
Lab 4 - RenderForm and SaveToSharePoint
Lab 5 - Transform

Day 2:

Lab 1 - Activate and Authenticate External Users
Lab 2 - Reusable Template Part

Day 3:

Lab 1 - Create a Dashboard
Lab 2 - Autheticate Mobile Users using Twilio XTP

Day 4:

Lab 1 - Add Prompts to your form using qRules
Lab 2 - Create an Overlay

Please email Support@Qdabra.com if you need any help with any of the techniques.

Re: Cascading Drop-down Value not Auto-populating Additional Fields

Jacob Russ — Thu, 13 Sep 2018 13:23:18 GMT

Hey Hilary,

Thanks for responding :)

I have attached the form in question. Please note that in order to simplify my post before, I claimed "State" was the third tier of the cascading drop-down. In actuality it is SalesOrg. I just didn't want to go into explaining what that is, but it is a field specific to my company and the way we organize selling regions.

In order to test the form, you will need to set the following values in the form:

Rule 1:

Type of Request: Request New BPID

RA Sales Region: EMEA

Country: AE - Utd.Arab Emir.

Sales Organization: 4004 - UAE

Use Default Sales Org Values: TRUE

Rule 2:

Type of Request: Request New BPID

RA Sales Region: NA

Country: US - USA

Sales Organization: 1000 - US

Use Default Sales Org Values: TRUE

You will also notice that I attempted to implement your "Trigger" solution found elsewhere on this site. It also didn't work. :)

Also, to be clear, I would DEFINITELY PREFER that the cascaded drop-downs system were only 2-tier, and the Sales Org values were populated automatically using rules (consequently populating the other 3 fields as well) off of the Country field. The problem here is that, despite there being a many-to-one relationship between countries and Sales Orgs, there are currently 252 countries on this great planet of ours - even if there are only 75 Sales Orgs here at my company. And that sounds like an awful lot of rules to create - even if I was able to get it to work.

AND SO...I created an XML Table yesterday containing all of the columns that I need to auto-populate for each country. I created it in Excel 2013, saved it as "XML Spreadsheet 2003 (*.xml), manipulated the header until it became readable by InfoPath, uploaded to SharePoint 2013 Online, and then created a new list for testing with single line of text columns. Opened in InfoPath, created the secondary data connection, converted the controls, and linked Region and Country to the XML table. I created a rule with no condition (field changes) to set the SalesOrg as follows:

xdXDocument:GetDOM("XML-Values_XML_V5")/ss:Workbook/ss:Row/ss:SALESORG[../ss:COUNTRY = xdXDocument:get-DOM()/dfs:myFields/dfs:dataFields/my:SharePointListItem_RW/my:Country]

This was as per another of your solutions for someone (do you recall Role populating Model User?) It also didn't work. I am thinking that I need to establish relationships in the XML file, but I still need to research how that is done.

Thanks for taking a look at this for me!

-Jake

Cascading Drop-down Value not Auto-populating Additional Fields

Jacob Russ — Tue, 11 Sep 2018 16:36:14 GMT

I have an InfoPath 2013 browser form that I generated from a SharePoint 2013 list. In it I am utilizing cascading drop-downs for Region, Country, and State. So when somebody selects a region (AP, EMEA, LA, or NA), the list of subsequent countries that are available for selection in the Country drop-down contains only relevant country values for that region. Same deal with State. These are both working great - I created a Region List, then a Country List that contains a lookup column from the Region list, and then a State list that contains a lookup column for the Country list. I brought these in as secondary connections and added a Region filter to the Country drop-down, and a Country filter to the State drop-down. Works like a charm.

The problem is when I want to create more than one rule for auto-populating a few additional fields based on the value in State. Currently, when a State value is selected from the drop-down, values are populating in 3 different fields, using a single rule. But as soon as I add a second rule for another State value, I run into the following trouble:

1. When "Don't run remaining rules if the condition of this rule is met" is not ticked for either rule, then selecting either one of the State values in the form will invoke Rule 2 and the 3 fields will end up being populated with the values specified in Rule 2.

2. If "Don't run..." is ticked for Rule 1 and not for Rule 2, then the Rule 1 State populates the fields with the Rule 1 values, which is correct and what we want, and the Rule 2 State also populates the fields with the Rule 1 State values, which is what we don't want.

3. If it's ticked for Rule 2 and not for Rule 1, then the fields all get the Rule 2 values, like #1 above.

4. If it's ticked for both rules, then the fields all get the Rule 1 values, like #2 above.

Another piece of info...I can't get the values in the State field itself to trigger these rules for the 3 auto-populating fields, so I am (very unfortunately) adding these rules to a Yes/No checkbox. If you'll recall, the State field is part of a 3-tier Cascading Drop-down relationship. Uncertain if this is relevant or not.

Here is the logic for the 2 rules:

Condition:
[Checkbox] = "TRUE" OR [State] contains "State" (AND doesn't work here for some reason)

Please note that I am unable to use "=" (instead of "contains") and "Type text..." here for the value, since this is a drop-down value and it is being seen as an integer I believe (ID?). With an operator of "=", I only have these options: "Type a number...", "Select a field or group...", and "Use a formula...". I am, however, able to instead refer to the original State fields in the data connection (as query fields or as data fields) and take advantage of the "=" operator along with a text string for the value. The behavior of the 2 rules is exactly the same as above. Again, uncertain if any of this is helpful, however.

Rule Type:
Action

Run these actions:*
Action: Set a field's value; Field: Autopop1; Value: Value
Action: Set a field's value; Field: Autopop2; Value: Value
Action: Set a field's value; Field: Autopop3; Value: Value

What am I doing wrong? Does anybody have any ideas? Thanks in advance-

-Jake

Re: Dynamic Drop Down in SharePoint using InfoPath

jivesph — Thu, 24 May 2018 05:12:56 GMT

I followed this guide - http://www.infopathdev.com/blogs/greg/archive/2005/07/14/Create-a-Repeating-Cascading-List-from-a-Flat-Data-Source.aspx it works for 1st and 2nd drop downs but it doesn't work for 3rd drop down.