SFTP trigger stopped triggering - azure-logic-apps

One of my Logic Apps is triggerd by the SFTP trigger. Today I changed the watch folder to a different folder, and I can't get it to trigger any more. I had the issue previously and had to create a new SFTP connector. This time I was able to resolve it by creating a new Logic App with all the same logic as the original. This is simply not acceptable. Its as if when programming if your program stops working your only recourse is to write it from scratch. How is one supposed to diagnose a trigger not triggering? I don't want to be faced with trowing away all my work again in the future.

Did you change the path using design view or code view?
When using the Code View, You need to make sure you are also updating the folderId and the metadata properties.
folderId is a Base64 encoding of the path. The same for the first property the metadata object.
When using the designer view, it seems that the trigger state (required to be able to recognise new items) is better refreshed when browsing through the folders on the SFTP trigger box (as opposed to just changing the path string)
HTH

Related

Azure LogicApp OneDriver trigger not working for large files (>50mb)

I have a azure logic app where the trigger is a OneDriveForBusiness connector that is watching for files to be created in a onedrive folder. Normally this works fine. However for large files (narrowed down to 52,397,814 works, 52,590,945 doesn't) the trigger never fires and shows as "skipped" in trigger history.
Has anyone seen anything similar?
Any suggestions on how to proceed?
Any suggestions as to a better place to ask about this?
My current plan is to switch to using a ZIP'd file... but I'm unhappy that there's an unknown upper limit after which file creates are ignored.
Thanks!!!
This is a known limitation:
The When a file is created or When a file is modified triggers will
skip every file bigger than 50 MB.
Depending on your requirements, you either need to find another way of signalling that a file has been created, or you can run the Logic App by schedule and check if new files appeared, or you need to change the approach altogether.

Is it possible to change config spec but only update partially

I have a huge clearcase snapshot view including about 10 VOBs, and it takes more than an hour to update the whole view.
Now I'm trying to change the config spec a bit to select several file elements with another timestamp. But by default, changing config spec will trigger a whole view update which is really slow. What I need is just to update the file elements with the updated timestamp.
I read through the official document about cleartool setcs, and also googled some time but it seems impossible. So Here's my question. Is it possible to change config spec of a snapshot view but only update partially?
Actually I also got a workaround here.
I opened the snapshot view in ClearCase Explorer, changed the config spec, clicked OK to update, and then cancelled after the update started. After that, I just updated those selected file elements.
The workaround was OK just for readonly. But I could not checkout/checkin because of the abort of update. The following error popped up when trying to checkout. So I had to update the whole view again.
An update appears to have been aborted or errors were encountered during an update. An update must be performed on the element to enable
a checkout.
Hence, here's another question. Is there any "brute" way to avoid the error for the workaround, since I know the config spec change won't affect other elements?
Besides, any other idea or workaround to solve my problem is absolutely welcomed.
One workaround would be to use a dynamic view (at least to try different config specs and check that the right versions are selected, before using that config spec on a snapshot view if you must.
Another approach is to use 10 snapshot views, one per Vob, because you can update them in parallel, making the all process faster, and starting some of the checkouts faster

How do I update a SharedResources.resx file in DotNetNuke 7

I am trying to edit a SharedResources.resx file for the ViewProfile control in DNN 7.
The file path is \DesktopModules\Admin\ViewProfile\App_LocalResources\SharedResources.resx. The default profile view has an 'Avatar' image which we are not implementing and I would like to remove the [PROFILE:PHOTO] token and surrounding image tag.
I am able to do this manually, but the page never seems to update with my changes.
So I go into the Language Editor and do the update there. However, when I click Save a new file is created called SharedResources.Portal-0.resx and my changes are saved to that file and are still not applied to the site.
The other resource files (type filename.ascx.resx) do not display this behavior. If I update a value it is reflected upon page refresh on the site.
I would like to know why this is happening and what the correct method of updating files of this type is.
Thank you.
You could try editing the SharedResources.resx file manually, instead of through the language editor, and see if that change takes effect.
The thing to keep in mind in doing that though, is that the file will be overwritten the next time you do an upgrade of DNN, so you would need to modify that file again.
By changing that file however, you can at least see if the change takes effect, if it does not, than would have to believe the info is somehow coming from a different location.

Check CopyLocal property of all references post/during build in multi project solution (Multi Xap)

I have a Silverlight solution that has multiple silverlight projects (Views) that all compile to their own .Xap file.
There is one "master" project that handles the dynamic downloading of the Xap files, which works pretty well.
But now I need to make sure that all the references are set to CopyLocal=false in all the View Projects. Only the "master" project can have CopyLocal=true.
This means that the Xap files generated by the Views stay rather small.
What I would like to do is check post or during the build process to see if any of the View projects have a reference with CopyLocal=true.
What would be a smart way of doing this? Using an external tool in the Post Build event? Or perhaps an addin for Visual Studio ? Or creating a macro in Visual Studio for this?
I have looked at using .extmap with assembly caching, but since you have to specify the assemblies in that, this does not solve my problem. I just need to know if there is a reference with the wrong setting and report that. Fixing it is not the question, that will still be done manually. It's just the notification I need.
Solution has 35 projects now, so dont want to check them all by hand every time.
I found a question similar to this one, but it lists msbuild as a possible solution. I would like to know if there is a way to do this using "code" (be it prebuilt in a tool/addin or otherwise)
I have chosen to go the Addin path. I created an addin that listens to : BuildEvents.OnBuildBegin
Whenever that event fires I create a list of all projects in the current solution. Doing a bit of recursive searching since there are also Solution folders that make life in DTE world a bit harder.
Then I loop through all the projects and cast them to a VSProject so I can loop through all the references.
Anytime I come accross a reference that is wrong, I create an ErrorTask where I set the Document property to the full solution path of the reference. To do this I Build the path for the project this reference is in, all the way up to the root of the solution.
The ErrorTask is then sent to an ErrorListHelper class I created, that handles the ErrorTasks and also performs navigation.
If I'm done with all the projects and I found any errors, I cancel the current build and show the Error List window, where my ErrorListHelper holds all the Reference Errors I created.
Whenever I want to navigate to the Reference in question, I activate the Solution Explorer window and get the root of it using an UIHierarchy.
Then I walk the path from the root on down, step by step, using the UIHierarchy to get to the UIHierarchyItems and expand them. Until I get to the deepest level (the reference) and I Select that.
Since I only need it for a certain solution and within that solution for certain projects (.Views.* and .ViewModels.*) I also have some checking for those in place during buildup of the Error List.
It works like a charm, already found 12 "wrong" References in 35 projects where I tought all were well.
I am using a different path now to do this. I have a base class that I can use to write unit tests that have access to the DTE2 object. This way I dont need an addin. This also works for Silverlight projects since the test class does not actually need access to the Silverlight projects, just being in the solution is enough to be able to iterate through the projects and check the references.

Auto update dialog / Notification for WPF Application

I want a automatic update notification in my application. A message box should appear which tells that an update is available, if user wants then it can download the latest version in downloads folder of windows. Nothing else (user will install it manually) not application.
-I'm using Installshield so no Click once solution.
Thanks
If you want an out-of-the-box solution to this problem you're likely to be disappointed. I haven't found anything that works except ClickOnce, and I dislike it. I did find this:
http://windowsclient.net/articles/appupdater.aspx
My solution was to roll my own. It's actually not that difficult. I wrote a small bootstrapper application that first checks for updates, downloads them if necessary, and then launches my application in a new AppDomain. Pretty easy.
If you want to check for updates while your app is running, you need to write and add a component/class to your project that performs that task, and informs the user (MessageBox or whatever) that an update is available. If they choose to perform the update then you need to launch your bootstrapper (so it can fetch the updates) and kill your current process.
All of this is very possible with a little time and some custom code. It's not as difficult as it sounds. The biggest thing is determining how configurable you want your custom solution to be because that can affect when/where your bootstrapper goes to look for updates (I built mine to look for updates on a network share).
http://autoupdatewpf.codeplex.com/
i found one. This one is quite simple and solve the purpose.

Resources