Plusautomatisering Posted February 13, 2012 Posted February 13, 2012 Hello, I would add a new portal row button on each row when i'll click on it it must add a new portal row under the row the button is placed. Any suggestions? Thanks,
bcooney Posted February 13, 2012 Posted February 13, 2012 Your request is not clear. If you are expecting a portal within a portal, then you will be disappointed because that is not possible. Perhaps a list view with a wide body part and a portal in the body part? Please provide a bit more of what you are hoping to design.
Plusautomatisering Posted February 13, 2012 Author Posted February 13, 2012 No it is not a portal in a portal. Just a portal to one table. What i'm trying to establish is when you press the green button there must be add a new record underneath it. I'll enclosed to file. user : admin no password WeekPlanning.zip
bcooney Posted February 13, 2012 Posted February 13, 2012 You don't need a button to add a portal row. Just turn on Allow Create in the relationship. However, if you'd rather not have that on, then the script would look like this (not real code): Set $parentID, ParentKeyID go to child table new record set foreignParentID field, $parentID go to original layout
Plusautomatisering Posted February 13, 2012 Author Posted February 13, 2012 I don't think you onderstand me. I'll make for example 5 rows then i'll would like to add a new one between te first two.
bcooney Posted February 13, 2012 Posted February 13, 2012 I see. Cannot do that. This isn't Excel, there's no insert row. You can, however, sort the portal so that the "new" row ends up in the proper location in the list.
Plusautomatisering Posted February 13, 2012 Author Posted February 13, 2012 I know how can i sort the portal so the rows ends up in the proper location? Did you see my file i'll included ?
bcooney Posted February 13, 2012 Posted February 13, 2012 OK, looked at the file. imho, you shouldn't store text values in your join table, but rather IDs. Also, your interface leaves holes in your join table. You are not creating proper join records, if you intend for the personnel to be related to the project. I would approach this using a side-by-side portal. The first portal would have the list of projects. Select a project and populate a global field (or $$var). The second portal would show all related personnel for that projectID.
Recommended Posts
This topic is 4666 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now