Exporting Portal Rows

[Bell Boy]

I'm totally pulling my hair out.

I'm trying to export a sorted portal which contains 54,858 records out of a total 130,000 records.

Each time I try to export the records, I get 65,548 records.

My export is set up to export from the current layout and I have chosen the fields associated with the portal.

Can anyone tell me what I am doing wrong?

[comment]

This is not very clear. Wherever there's a portal, there is a parent table and a child table. Which table has the 54,858 records?

In general, if you are exporting from a parent layout and including related child fields, the number of exported records will equal the number of child record related to the parent records of the current found set (this is assuming the export is to a text file).

[mr_vodka]

where are you exporting the records from? If you are talking about exporting the portal, then you are most likely still on the parent layout. You should GTRR ( Go to Related Record ) using the portal relationship and then export out from a layout based off the Child's TO.

[Bell Boy]

Okay.

I've uploaded a copy of the file minus around 100,000 records. File size was huge.

I do have a Parent table (actual name)

There is a relationship to another table called "Temp Stores" which is based on a constant(1).

Then I have a relationship from "Temp Stores" to the table "Mailing_List" which is based on "store_id" and "miles_from_store". The portal that I am trying to export is the Mailing List portal. It does export, however it is giving me more records than it should.

Thank you for the help.

Mike

MailingList.zip

[Bell Boy]

Hey Vodka,

Thanks for the help again.

You are correct.

The layout is based on the Parent table.

So, what you are saying is, I will need to create a script that will match up each record in the portal with a layout based on the Mailing List?

The Mailing List is the portal based list I'm trying to export.

Mike

[comment]

Why don't we start with the fact that your relationship from Parent to Temp_Stores is invalid (the matchfield in Temp_Stores being a global)?

[Bell Boy]

I just answered my question to you.

I made one of the fields on the portal a button, set it to G to Related Records - matched all records in set.

And it works!

Thank you for pushing me in the right direction.

Mike

[Bell Boy]

So, having a global field as part of the relationship makes it invalid?

Hmmmm. Seems to be working though.

Any suggestions?

[comment]

Seems to be working though.

Could be, but you are playing with fire. IIUC, you want a relationship from all Parent records to all Temp_Stores records? In versions before 7, you would do this by having a STORED calculation field =1 in both tables. In version 7 and higher, you can use the "x" relational operator with any two fields.

[bruceR]

I'm totally pulling my hair out.

I'm trying to export a sorted portal which contains 54,858 records out of a total 130,000 records.

Each time I try to export the records, I get 65,548 records.

My export is set up to export from the current layout and I have chosen the fields associated with the portal.

Can anyone tell me what I am doing wrong?

1. It's hard to say since we don't even know what in fact you are trying to do. What ARE you trying to do?

2. Besides the specific problem of the global calc, you seem to have just thrown tables at the graph. Looks to me like about half the graph should disappear. For instance what is the purpose of Store States and Store States 2? Why isn't Temp_Stores called Stores? What is the purpose of the entire bottom row of the graph? What is the purpose of Parent?

See attached modified example for my idea of what you're trying to do.

MailingList.zip

Edited April 23, 2008 by Guest
Added attachment