Newbie Questions

Re: referencing data from repeating sections

murphythadog — Fri, 20 Feb 2009 16:03:43 GMT

Yay I'm done. Now I need to show them what I've done; see if they like it and turn it over to some real programmers (this means someone besides me the network administrator). Thanks for everyone's help on this especially Jimmy.

Re: referencing data from repeating sections

Jimmy — Fri, 20 Feb 2009 02:04:05 GMT

It looks like you still have filters on both repeating sections in the TOC.

Once the filters are removed, the default value of TOC/TOCgroup/AutoNumber should be:

count(../preceding-sibling::my:TOCgroup/my:AutoNumber) + count(../preceding-sibling::my:TOCgroup/my:group2/my:field1) + 1

Re: referencing data from repeating sections

murphythadog — Thu, 19 Feb 2009 16:25:36 GMT

Updated XSN attached. Why is my TOC autonumbering starting with 6? I can't seem to get it to start with 1.

Re: referencing data from repeating sections

murphythadog — Wed, 18 Feb 2009 20:33:33 GMT

Got the second one working, I'm still working on the TOC autonumbering.

Re: referencing data from repeating sections

murphythadog — Wed, 18 Feb 2009 17:04:28 GMT

I removed that filter. I had tried to use a filter to filter the data for Admin Services and Inpatient Services and didn't have any luck.

Re: referencing data from repeating sections

murphythadog — Wed, 18 Feb 2009 13:55:36 GMT

I think that was a left over from something I was trying to accomplish that didn't work. The TOC is a summary of all different types of rooms that can be filled out in the form.

Administrative Services:

Administration
Education Center
Employee Services
Information Services
Lobby Services
Medical Records
Etc.

Diagnostic & Treatment Services

Emergency Department
Diagnostic Department
Laboratory/Specimen Collection
Surgery Department
Etc

Inpatient Services

Acute Care Unite A
Acute Care Unit B
Critical Care Unit
Obstetrics
Etc

With the filter I was hoping to get only the data from each area but I could never get it to work. So I decided since I'm going to be filling out the form and saving it as a template, then saving the form as source files then I would go ahead an set up the TOC manually, since I couldn't figure out how to do it automatically.

The autonumber for the first part seems to work. Is there a way I can get it to reset for every new Section? For instance When I Add a new area it keeps counting up.

Re: referencing data from repeating sections

Jimmy — Wed, 18 Feb 2009 03:57:54 GMT

I'm a bit confused about what you are trying to do on the TOC page. You have a filter set to only display rows where SectionTitle is equal to "Administrative Services", but you are allowing users to insert rows and select the SectionTitle from a dropdown box. This is a bit of a contradiction.

The reason the numbers are skipping is that when the form loads, a row is being hidden because its SectionTitle is blank, and not equal to "Administrative Services".

Re: referencing data from repeating sections

Jimmy — Wed, 18 Feb 2009 03:36:16 GMT

Please change the default value of DepartmentSection/Services/AutoNumber to:

count(../../../preceding-sibling::my:RepeatingServices//my:AutoNumber) + count(../../preceding-sibling::my:DepartmentSection//my:AutoNumber) + count(../preceding-sibling::my:Services//my:AutoNumber) + 1

Change the default value of DepartmentSection/TotalNetArea/AutoNumber to:

../../my:Services[last()]/my:ServicesTable[last()]/my:AutoNumber + 1

And change the default value of RepeatingServices/OptionalArea/AutoNumber to:

../../my:DepartmentSection[last()]/my:DeptGrossArea/my:AutoNumber + 1

I'll be back to help with the other view later on, but tell me if there are any troubles with the above.

Re: referencing data from repeating sections

murphythadog — Tue, 17 Feb 2009 21:34:50 GMT

I re-worked my whole form once again. I think it's good enough to submit, but some how I hosed up my auto-numbering and I can't seem to get it right on a couple of views. The 01A_TOC View and the 02_Main Input for Services view. These are the only 2 with autonumbering.

I went ahead and tried a couple of times without success. The 02_main view is tricky because it needs to reset itself for every new "service" as I call it.

Re: referencing data from repeating sections

Hilary Stoupa — Tue, 03 Feb 2009 16:18:44 GMT

Hi--

There isn't an out of the box way to get drop down values from more than one data source. One way around this is to use two (or more) drop down controls, and use conditional formatting to show the correct one. Another thing you can do, if you are using SQL (or Access, I believe) to store the data that is used for the drop down values, is create a view that combines the data sources. And, of course, you can always use code.... add an xml file as a secondary data source that has a repeating structure:

<?xml version="1.0" encoding="utf-8"?>
<Util>
      <row>
            <value></value>
            <display></display>
      </row>
</Util>

Use it for your drop downs and populate it in code with the values from your other data sources. Hey, I did download and take a look at your form -- you seem to have a lot of unbound controls you should probably address (the ones w/ the red x in the corners....)

Re: referencing data from repeating sections

murphythadog — Fri, 30 Jan 2009 17:06:33 GMT

I think I'm on the home stretch of my form. I'm at the Stacking Options part of the Form. Which is luckily the last part. Basically the Stacking Options will be the whole TOC Summary rearranged per floor. For instance you can either build the building all on one floor or stack it up higher. The reason for stacking options is to give the customer the ability to choose what's best to fit on a property or future property.

I'm sort of stuck on how to do a drop down list of multiple groups. I can get it from one repeating group but not multiple repeating groups. I will attach my latest form to see if anyone has any ideas.

Re: referencing data from repeating sections

murphythadog — Wed, 21 Jan 2009 21:59:05 GMT

Well that worked for the drop down. I think I will need code for the summary though, because my thinking is the stacking will need the drop down and now that I know how that works it looks like it is perfect for the stacking.

The Summary sheet I think will need coding for the autopopulating. I can't seem to force it to look beyond the AdminSuite for autopopulating. Where its automatic.

Re: referencing data from repeating sections

murphythadog — Wed, 21 Jan 2009 17:39:50 GMT

Here is the latest and greatest. I haven't had a chance to try what you suggested, just wanted to post my latest data source since it changed so much from the last one.

Re: referencing data from repeating sections

murphythadog — Tue, 20 Jan 2009 15:34:39 GMT

I should have updated my XSN earlier, because I rearranged my data source a little to try an accomplish my task here. It didn't seem to help. I would post it, but I'm actually a jobsite in NJ setting up routers, switches and a couple of users. I don't have access to the server my xsn file is on, so I will try and upload it tomorrow when I get back. I will also try the method you described. I think I'm leaning towards auto-populated textboxes for the Summary page and I will probably want to do Drop Down boxes for the Stacking Options page which isn't even built yet.

Re: referencing data from repeating sections

Jimmy — Tue, 20 Jan 2009 14:56:40 GMT

I think there might be a way to get those numbers right without using code. I am experimenting on the form you attached in the 4th post of this thread.

Open up the Dropdown box's properties, click the button next to Entries: and select the AcuteCare node.
For Value, click the button and select AcuteCare/DptDGA/Total
For Display, select AcuteCare/Header/Sheet

Then delete the field9 textbox from the table, and replace it with an expression box bound to field7.

This should get you the behavior you described in your initial post, but not the dropdown box behavior or autopopulating you described later. Anyway, give the above a try and let us know if it will be sufficient or if we should start digging into code.