Duplicate Items In The Irrigation Schedule

Great response Jer. As I was reminded today by Mike Bennett today, "Everything is prioritized." I totally trust you and the rest of the LandFX team to prioritize effectively. The other things on the list that you mentioned are very important too. Many are on my personal wish list. And I believe that there is not a software developer team that comes close to the Wizards at LandFX.

Now, relative to importing from previous projects, we love that LandFX offers this option. It's so nice to import a piece of equipment and have the associated detail come into the project with it. It works great with the reference notes as it allows the user to select the specific element and the accompanying detail. That's a great time saver. - it's the problem with importing ALL of the equipment in the project that we have with the import from project with the irrigation elements. If we wanted to do that, we would use a template which is also a good option that LandFX offers. We use that option for certain projects (agency specific or type specific projects).

I'll look forward to having this work effectively in the future, but will continue to trust LandFX prioritization. I'll try not to mention this issue for a while.

Steve

This is definitely still on our radar, and we will be re-engineering the import system.
But just as you describe, it is not an easy task, as it needs a dialog and the ability to reassign symbols.
And if we were to step back for a second, why are you using Import on practically every project. It sounds like the main reason is just a minor schedule formatting issue. It would actually be far easier for us to add this option to the schedule -- to have it list the category, and put the make/model with the description.
It is worth noting that we deal with many irrigation tech support tickets that are due to importing the equipment from a previous project, rather than adding from the master database. Our preference is absolutely to always add from the master database, that way we can assure that it has the most accurate possible data. We fix issues in the master database literally every single day - what we cannot do, is to dive into all users data and fix that issue across all of their projects. So there is an inherent risk in importing from previous projects.
We also have plenty of other wishlist demands that are just as serious - requests for the Watering Schedule to be able to be set in Minutes, an ability to include Wiring on the Irrigation Schedule, an ability to rotate a plan after placing Spray symbols, a Symbol Explorer to aid in customizing symbols, Ag layout tools for our Dripline, integrating MAWA and ETWU calcs, and that is all just off the top of my head. We spend a good deal of time just trying to prioritize wishlist items.
So, that all being said, as I mentioned, this is still on our radar, and a fancy new Import dialog box should be rolled out in the next few months.

--J

I'm still not satisfied. It seems like this happens on every project now. Why does it let me choose individual items when I'm importing items for refnotes, but when I want to import an irrigation auxiliary equipment from another project, it brings them all in? This is where the conflicts are originating. Please give us the choice as to what to import just like refnotes. And then have it check to see if something is already using that block. If it is, then prompt us to use a different block. There can be tons of auxiliary equipment in every project. chances are they will be assigned similar blocks. Especially in the "other" category which are mostly user added elements. - Please lets get some help with this. I know not today, but soon please.

I understand that this is not an easy task. For instance, how will the program know if we have already added this part? Our office switches out the actual part with the generic item. As an example, we call the part in the heading "Electric Remote Control Valve" not "Hunter ICV" and the description begins with "Hunter ICV". See the attached. BTW, This way of noting the irrigation elements is both traditional and still common. - See the attachment.

BTW, We're coming up next Thursday to go to the street market. Maybe I'll stop in on Friday to say hi. And maybe you and some of the LandFX team will meet us at the concert in the Plaza Friday the 13th to see Brass Mash. https://m.facebook.com/events/404811170954401?active_tab=discussion. That was fun last time.

Seaweed,

I'm back from vacation!
As for "fixing" this - we have scheduled to revamp the Import feature in the Irrigation Manager, to use a dialog box, and address multiple issues. But in all honestly, we're not going to be able to address all issues. When it comes down to it, when you are Importing into a project that already had equipment in it, you are always going to run the risk of some sort of conflict between what is already in the project and what you are importing. We could make Import only work if there is nothing already in that section, but obviously that wouldn't go over too well.
We should get the revised Import functionality within a month or two.

--J

Jake,
Thank you for sharing the link..

I went through it but not sure if it is a bit long process specifically if you are in a strict time of submission, and the last thing you need to worry about is to fix the schedule.
this is my concern about this link.

I fixed it the easiest way, I did delete the advised equipment an add it again, then I generated the schedule and it worked perfectly(attached BEFORE & AFTER the fix), but not sure if this is right.

I would recommend that if there can be an internal fix in the program for this problem as Seaweed said.

Nibal

Jake and Jer,

In my opinion, this is happening way too often. Please adjust the program so that this link can be removed from your white pages. It happens way to often. Can't the program just check to see if the element is already used in the project? If it's used as a component, let the elements that have not already been used in the project be installed and the others should not be allowed to be duplicated. There's got to be an internal fix.

I just had this happen again (went through the last submittal messed up). Instead of going through this whole rig-a-marrow, I created a new window in the paper sheet to cut the extra element out. Not a good fix. I know. But takes a lot less time. Not a good fix. Shouldn't need a user fix. Sorry to throw this back at you, but you're the smart guys in the room.

Maybe when I'm up there from the 12th to the 16th you can tell me that this is already done (probably not though as I know that your plate is full already). We'll be going to the concert at the plaza again. It would be great if any of the LandFX team will join us again. That was so fun last time.

Seaweed

Nibal,
Please follow the steps in the link provided and you should be good to go. If you run into any other questions or issues feel free to submit a Tech Support ticket with your files and we can help you out.

Irrigation Schedule Shows a Duplicate Symbol and Quantity for Certain Equipment