So I have a document library with date, alert and alert-date fields.
The date and alert fields are completed when a doc is uploaded, and there is a workflow which takes the alert away from the date (and also takes an extra day off) and sets it as the alert-date. E.g. If the date is 15/07/2013, and the alert is 1 month, the workflow sets the alert-date to 14/06/013 (15/07/2013 - 1 month and a day). The alerts have options of 1 month, 3 months, 6 months or 1 year. A extra day is always taken off as these workflows are triggered by information management policy which only allows conditions of +1 day (the day is taken away via the workflow and then added via information management policy).
The problem comes when a .docx file is uploaded, as all the alert-dates (even if they relating date and alert aren't populated) are set to 01/01/1900.
I know SharePoint workflows pretty well and have never come across this problem before, so was just wandering if anyone else has and knows a solutions?
Thanks,
Josh.
Found a solution:
The alert-date fields didn't seem to be set at the same time that the workflow was looking them up (for docx files). So I added a minute pause at the beginning of the workflow which gave enough time for all the dates to be set and then for the workflow to look them up, and there are now no issues.
Thanks,
Josh.
Related
I have a pdf file that was created on a certain date and from the meta-data it was last modified on a date after its creation.
The pdf is nearly all just text and there is a sentence in the text that has likely been extended and a word deleted. Can I find out whether this particular sentence was in fact (likely) modified between the creation date and last modification date? Or rule it out.
I didn't know whether I could convert the pdf to a more elementary type (similar to .tex) or view it in another more elementary application (like CosEdit) to identify whether this sentence was extended and words deleted between the creation date and last modification date?
Don't worry about anyone attempting to conceal the modifications in any way. That's not applicable in this instance.
Link to document: https://drive.google.com/file/d/1OFXRCw2U1mo7BjHUSGs_1fVjDsQLRo0V/view?usp=drivesdk
Realvent line is on page5. Its the first bullet point under the title Criteria for Addressing a Property
There is not much value or certainty when analysing a reasonably well constructed PDF the sample provided is of unknown pedigree. I personally would not trust a PDF history comparison over a conventional Paper Trail. You query the changes made to a newer copy of a Public Document.
We can see the Original was reported as produced by the technician using Word 2013 on 6/12/2017, potentially after drafts had been corrected by management, the source document reports that there were 2 prior changes, which are not of concern here, since the document as it stood at that time, would then (as if printed) have gone forward for final approval, master sign off, and publication.
You provided a secondary amended copy of the same policy document. Initial query shows it appears as if it was subject to A change in time but there are no incremental editions to be pared back, so using a comparison tool we can check for the differences.
First look suggests 5 of 8 pages were changed (updated per annual review)
The first change is Page 3 the admin charge for 2021 is now £86 (was £75 in 2017)
The second change is on Page 5 more on that later
The third change is on Page 6 where premise has been changed to primary
The fourth is Page 7 where the example Numbered ... 1 is changed to Lettered ... A
Finally Page 8 the Technician has been Promoted over the years and the department has been renamed.
ALL these changes would have been made in the source Word Document which in turn may have changed many more times than we shall know without the paper trail showing which day the technician was formally appointed or the department changed name or the annual charges were increased. A PDF is dumbly generated as showing A difference from the original.
Your query is can we tell how many times or when or by who Page 5 was changed. As you may have gathered from the above the short answer is usually no (not from a PDF).
The changes over time of a policy document are driven by many factors such as inflation, spell checking and proof reading changes, or changes in managerial policies.
Page 5 was changed in two places
semantically the unnecessary word "new" was replaced with "a"
and a concession was added to the end of the paragraph
"unless justification can be supplied"
There is no way of knowing who penned those changes, only some certainty we can guess the technician was directed to make those corrections between 2017 and 2021. But was it verbal or by email or paper we do not know those are other documents. What we do know is the final document must have been approved for PDF printing, unless your copy is unofficial.
If you wish to know more see https://www.whatdotheyknow.com/request/street_naming_information
Could anyone provide any best practices about multiple migration runs? Moving from TFS 2017.3.1 to Azure DevOps Service. Dealing with a fair number of work items (32k). Of course, TSTU throttling is making the run take a long time, so I was thinking of pushing what I could up front, then a second pass to pick up the new work items since the first big push. So...enabling UpdateSourceReflectedId would set the ReflectedWorkItemId on the source items that have already been migrated. But what happens if someone changes a work item that has already been pushed? Would the history delta get picked up? How is that typically resolved...I was thinking maybe a Querybit like: ReflectedWorkItemId <> '' and ChangedDate > (last run time), but is that necessary? Those already exist on target...would ReplayRevisions pick up only the missing changes? TIA...
I usually do the following for large runs:
Open work items edited in last 90 days
Closed work items edited in last 90 days
open out to more days in chunks
The important thing to note is that links are created only when both ends of the link exist.
After a long run you can then rerun "edited in last month" to bring any changes a cross.
Changes to avoid in the Source:
changing work item type
moving work item between team project
We handle these, but loosly.
I hope that you can help me.
That's my situation: daily I'm importing in Power Pivot some data through a query on a SQL database.
Actually every morning I open the Power Pivot and I refresh it for import the data of the previous day present in the database.
This action require 20 minutes because I have a lot of data to import.
I was wondering if there is a way to do this action during the night, maybe an automatic refresh, so that I can open the file in the morning and I alredy have the data of the previous day.
I hope that I was clear with my request, thanks in advice.
If the Excel workbook is on a machine that does not shut down, you can keep the workbook open and configure the query to automatically refresh ever x minutes.
Or you can keep the workbook open and run VBA code to refresh the query on a timer.
There are plenty of examples for VBA timers if you just care to search.
Or you can configure the queries to refresh automatically when the file is opened, then create a Windows Task Scheduler job to open the workbook at a specific time. Again, the computer running this must be turned on.
You see that there are many options and they are all well documented and just a short google search away.
I have one vb.net windows application and I want to deliver it to my client with 1 year validity.
After one year this software will automatically stop working or ask for renewal.
The client PC doesn't have internet access.
Please tell me the secure way for this.
When the program is installed, have it set a registry value with the current date. Then, on every subsequent program start, have it check that registry value against the current time. If more than a year has passed, do whatever you plan on doing to lock up your application.
This post has some excellent info on the specifics of adding, modifying, and accessing registry values in vb.net.
Check the date.
If dateToday > dateProgramSold.AddYears(1) Then
'open form that cant be close saying program is expired
End If
When the program is installed, it should ask for an registration key (they could get it by email, print it off and type it). The key should contain the last day of validity (encrypted). Store the key in the registry (or somewhere else). When the program starts, you check the date inside the key.
If they re-install the end date will stay the same.
When they want to update, just send a new key by email or mail.
The amount of security you put into just could depend on how much you trust the company. Because they could always decompile and crack your software.
I needed to do this for a program I wrote. My final solution included the resolution that you can't be 100% foolproof, so I considered my users and did the best I could with what I had.
Without access to the internet, how does the computer know what date it is? It has to rely on user input for it. So if a user can input it, then a user can change it. There is no foolproof way to get an accurate date from the PC without the the user having access to it. Whether from the OS, the BIOS, etc.
So what I ended up doing was putting an obfuscated key into the registry in an obscure place. HKCU >> Software. I made the key just some letters and numbers {L12A3C0DFF} then I named the key Z0B0 and made the value the obfuscated date. I took the year month and day and ran each one through a different calculation. I ended up with something that looked like DDE011468932.
Each time the program ran it decoded this registry setting to see if a year had passed based on the time in the BIOS. If the date in the BIOS was earlier then this date then they changed it and I would not not allow my program to run.
Also each time the program ran, I checked the date in the BIOS and stored this in the registry in the same way. So I would check to see if they changed the date in the BIOS to an earlier date.
So in order for them to abuse the date restriction of one year, they literally had to change the date in the BIOS every day which I figured was not worth it to them to do, besides, they would have had to figure out where I was getting the date from to begin with, which would take decompiling (and I wasn't selling it to a bunch of programmers). Simply changing the date in the OS wouldn't fool it.
We're using an Access application that stores and retrieves information from SharePoint, and the times and dates get viewed through the 'filter' of the Time Zone settings on SharePoint.
This has started to cause a problem when just trying to enter a date with no time. People marked as CST will see 7/1/2014 0:00, but those in PST will see 6/30/2014 22:00. Calculations that organise metrics by date would then show the same entry in June for PST users and July for CST.
Is there a way to adjust for this? I don't WANT to be capturing a time in this field, but since it's a Date/Time field on SharePoint, it's attaching a time anyway. Would changing the field in question to 'String' work or would that cause more problems than a more adaptive solution?
(I've read links that popped up in 'Questions that may already have your answer', conducted other searches on and off Stack.)
After a bit of testing after all my Users went home except for one, I found that just changing the type on SharePoint for the fields in question from 'Date/Time' to 'Text (Single Line)' worked perfectly. My Tester had no issues with the VB used to store information and bringing up the raw tables showed the 'proper' date stamps after a restart of the client database.
It seems a little too good to be true, but it appears to be a victory! I'll definitely come back here with an update if anything blows up.